Sometimes, when calling an API Endpoint triggered flow, a timeout error will displayed in the service or program that is calling the API endpoint. However, when verifying the flow history, it appears that the flow executed successfully without error.
- Okta Workflows
The service or program in use is waiting for a response from Okta Workflows, but the flow took an extended time to complete execution. Therefore, a timeout error will be displayed.
One way to manage the risk of a timeout is to close the HTTP connection as quickly as possible.
A best practice is to add the API Connector Close card as the first card in the flow.
This allows the Workflows engine to immediately release its HTTP connection to the caller (HTTP client).
Then the Workflows engine asynchronously processes the rest of the flow. See Close.
