I was checking the documentation and several articles and I have the doubt of when the Prometheus stop the retries on the Remote-Write configuration. Checking the Remote-Write settings I don't see any directly related with a limit (I guess Prometheus does not stop the retries when max_backoff is reached).

So we can read:

1. https://prometheus.io/docs/practices/remote_write/#remote-write-characteristics

When one shard backs up and fills its queue, Prometheus will block reading from the WAL into any shards.
Failures will be retried without loss of data unless the remote endpoint remains down for more than 2 hours.
After 2 hours, the WAL will be compacted and data that has not been sent will be lost.

2. https://grafana.com/blog/2021/04/12/how-to-troubleshoot-remote-write-issues-in-prometheus/

min_backoff and max_backoff: These are used to retry sends of a single batch of samples from a shard.
Because we try to not lose your data, retries are endless.

So my doubt is, does Prometheus ends the retries when the metrics are removed from the WAL after 2 hours?