Forward geocoding (when users override location manually) is getting overloaded and driving the recent forward_geocode: status_429 failures. Telemetry over the last 24 hours shows about 4.5k manual-address failures, including 4,487 LocationIQ 429s, with request volume peaking at 22 attempts per minute and a p95 of about 7 per minute. GPS users are unaffected. The minute-based refresh loop can keep re-hitting the same quota boundary.
The short-term fix is to persist the resolved lat/lon for unchanged manual overrides so we don't re-geocode the same string on every refresh. We should also add exponential backoff with a cooldown when LocationIQ returns 429.
We should also improve observability in Settings by surfacing the most recent failed fetch, not just the last success. That way it is obvious when a fetch was attempted, when it failed, and why.
Refs:
Forward geocoding (when users override location manually) is getting overloaded and driving the recent
forward_geocode: status_429failures. Telemetry over the last 24 hours shows about 4.5k manual-address failures, including 4,487 LocationIQ 429s, with request volume peaking at 22 attempts per minute and a p95 of about 7 per minute. GPS users are unaffected. The minute-based refresh loop can keep re-hitting the same quota boundary.The short-term fix is to persist the resolved
lat/lonfor unchanged manual overrides so we don't re-geocode the same string on every refresh. We should also add exponential backoff with a cooldown when LocationIQ returns 429.We should also improve observability in Settings by surfacing the most recent failed fetch, not just the last success. That way it is obvious when a fetch was attempted, when it failed, and why.
Refs: