RainWind120 — location, refresh and API usage

When an update needs a location, RainWind120 first tries GPS for up to 15 seconds. It can then use an eligible weather-observation or saved-location fallback while GPS retry windows continue. Once a precise fix is obtained, it is reused for that open session.

On opening, a forecast aged 10 minutes or more is eligible for refresh. Refresh checks also continue while the detailed view remains open. Valid data stays visible during updating; inside the app it is hidden at 15 minutes. An updating indicator appears while work is underway; a failure or unavailable message is shown separately.

Refresh setting — What happens

On opening — Default; no recurring schedule. The app may still finish an eligible unfinished refresh after you close it.

Every 15 minutes — Schedules background rain, snow/ice-risk and warning updates.

Every hour — Schedules hourly background updates. Opening still applies the normal ten-minute refresh rule.

The app’s background operation does not start GPS. It uses an available recent position or suitable fallback. Garmin controls actual background timing, so connectivity, battery and scheduling conditions can delay delivery. Wind and the Next 2–4h outlook are prepared when the full view is opened.

A fresh foreground refresh normally uses three calls. The app’s normal background refresh uses four. Warning details and retries add calls; reusable cached responses can reduce them. Every-15-minute background operation is about 384 calls per day before those additions.

Keep Stop at free limit enabled if you want the local guard. It counts dispatched requests, including failed, cancelled and timed-out requests, for this installation only. Its counter resets by UTC day; guarded requests resume no earlier than 00:05 UTC. It cannot see usage from another device or app, so also set OpenWeather’s provider-side cap.

Only missing or failed endpoints are retried. Each endpoint allows up to three total attempts, including the first, per rolling five minutes. The app does not repeatedly download every successful part because one part failed.