Add Resiliency and Retry Logic to API Call Actions in Rewst Workflows
Adam Fazakerley
Would it be possible to implement built-in resiliency for third-party API call actions (e.g., Microsoft Graph) within Rewst workflows? Specifically, when an API call does not return a successful 200 OK response, the action should automatically retry the request if the error is likely to be transient.
Common transient HTTP status codes that could trigger a retry include:
408 - Request Timeout
429 - Too Many Requests
502 - Bad Gateway
503 - Service Unavailable
504 - Gateway Timeout
The retry behaviour could be configurable per action, with parameters such as the number of retry attempts (x) and the delay between retries (n seconds). This would improve reliability and reduce the need for manual intervention when workflows fail due to temporary issues with external APIs.
Log In
Shmily Strasser
I believe this overlaps with https://rewst.canny.io/features/p/built-in-task-retry
But this feature would save so much time from having to add retry login to so many tasks...
Justin Leahy
I know some people will suggest making a sub-workflow to handle these errors but having to essentially remake the entire integration catalog to handle retries seems counter intuitive.
Daniel Kohl
We'd love to see this. We end up doing this ourselves with retry loops in workflows already, so it'd greatly simplify things if this was just built in.