riverpod-retry

Configure Riverpod provider retries by defining per-provider or global retry policies, including custom retry functions and safe exponential backoff behavior to recover from transient failures.

Yes, you can disable retry behavior for specific Riverpod providers by configuring the retry scope to exclude certain providers and distinguishing between ProviderException and generic Errors.

A custom Riverpod retry function signature allows control over delay and termination conditions, ensuring safe handling of ProviderException versus generic Errors during the provider computation retry process.

Exponential backoff in Riverpod retries safely increases the delay between subsequent retry attempts, preventing immediate repeated failures while allowing providers to recover from transient errors automatically.

Use global retry configuration in Flutter to apply uniform retry policies across the app, while per-provider configuration tailors specific retry scenarios and custom functions for individual Riverpod providers.

Riverpod providers retry to recover from transient failures, but you can control termination conditions and disable retries by properly handling ProviderException versus generic Errors in your custom retry function.