Okta Workflows API Endpoint Flow Times Out Despite The Flow Running Successfully
Last Updated:
Overview
An API Endpoint triggered flow in Okta Workflows times out when the calling service waits too long for a response. However, verifying the flow history shows that the flow executes successfully without errors. Prevent this timeout by adding an API Connector Close card at the beginning of the flow. When calling an API Endpoint triggered flow, the calling service or program displays a timeout error.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Okta Workflows
Cause
The calling service or program waits for a response from Okta Workflows, but the flow takes an extended time to complete execution. This delay causes the calling service to display a timeout error.
Solution
How is the API Endpoint flow timeout resolved?
Manage the risk of a timeout by closing the HTTP connection as quickly as possible. Add the API Connector Close card as the first card in the flow to allow the Workflows engine to immediately release the HTTP connection to the caller. Okta Workflows then processes the rest of the flow asynchronously. Review the Close documentation for more details.
Add the API Connector Close card at the beginning of the flow to prevent timeout errors:
- Authentication is not used on the Close card, but still needs to be selected in the dropdown. Create/Select an API Connection with None for the Auth type to enable clean flow configuration.
