Best Practices for API Call Retries in FlutterFlow

Hi FlutterFlow Community!

I'm exploring efficient strategies for API call retries and would love to hear your insights. Specifically, are loops necessary for implementing retry mechanisms, or is there a simpler method? How do you create a reusable template—perhaps through action blocks or another feature within FlutterFlow? I've had some pretty error prone results copying and pasting between action blocks (params/args don't register as incorrect when copied and this leads to some deep detective work on build failures). With multiple/non-blocking API, has anyone devised a system of retry counters, possibly creating a new item for each call? What practices have you found to be effective in managing retries without complicating the app state?

This is an open question on what works for you especially if you're working with a wide range of different apis in your apps. Thanks!

1
15 replies