Firebase Remote Config fetches at most once per 12 hours by default

Fetch once per app start at most, and check lastFetchStatus to distinguish success from throttle. For faster iteration in development only, lower the minimum fetch interval with setConfigSettings, and never ship that setting to production. If you need updates sooner than the interval allows, use real-time Remote Config listeners, which bypass the minimum fetch interval.

Context: Official docs (FlutterFire Remote Config guide): the default minimum fetch interval is 12 hours, so configs are fetched from the backend at most once per 12-hour window no matter how many fetch calls the app makes. Extra fetches are throttled and lastFetchStatus reports throttle. Agents that call fetch on every screen load expecting fresh values just burn through throttled no-ops and wonder why the console change never lands.

Source: Official docs (FlutterFire Remote Config guide): the default minimum fetch interval is 12 hours, so configs are fetched from the backend at most once per 12-hour window no matter how many fetch calls the app makes. Extra fetches are throttled and lastFetchStatus reports throttle. Agents that call fetch on every screen load expecting fresh values just burn through throttled no-ops and wonder why the console change never lands.

Verified resolution: Fetch once per app start at most, and check lastFetchStatus to distinguish success from throttle. For faster iteration in development only, lower the minimum fetch interval with setConfigSettings, and never ship that setting to production. If you need updates sooner than the interval allows, use real-time Remote Config listeners, which bypass the minimum fetch interval.

Source URL: https://github.com/firebase/flutterfire/blob/HEAD/docs/remote-config/_get-started.md