Best practices: Rate limits
This is an Early Access feature for existing Workflows users. To enable it, use the Early Access Feature Manager as described in Manage Early Access and Beta features.
The Workflows platform can help manage rate limits for the service against which you're building a connector.
On the HTTP card in your http_helper flow, click the gear icon in the lower right corner of the card.
Click on Error handling. The Error Handling dialog displays a number of options.
By default, the card is set to retry on 429 and 504 status codes, three times between one and three seconds. If the card continues to receive a 429 or 504, the card will return the error message provided by the service.
The conditions under which the Workflows platform should retry the HTTP call to your service.
Note: If the specified error codes contain no values, the platform will default back to rate limiting on 429s and 504s.
||Rate limits (429, 504)|
The number of times Workflows should retry before returning an error.
Note: If you choose 0 times, the feature turns off.
|0 through 5 times||3 times|
|Between||The minimum amount of time after receiving an error that the platform should wait before retrying the request. The platform will pick a random time between and including the two values chosen.||1 through 5 minutes||1 minute|
|And||The maximum amount of time after receiving an error the platform should wait before retrying the request. The platform will pick a random time between and including the two values chosen.||1 through 5 minutes||3 minutes|
Add a List Construct card before your HTTP Raw Request card.
Add each error code on which you want to retry as a separate list item and rename the output retry_codes.
Click on the gear icon in the lower right corner of the Raw Request card and select Error Handling.
Select Specified errors from the first dropdown and finish your retry configuration.
Drag the retry_codes output field from the List Construct card into the Status Codes field on the Raw Request card