An Okta Event Hook sends duplicate data to Workflows because the hook times out and triggers a retry. Respond immediately to the HTTP request with a success code to prevent the timeout and resolve the issue. An API Connector card configured with an Event Hook triggers multiple Workflows for the same event.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Event Hooks
• Workflows

The Event Hook times out, triggering a retry.

Okta Enforces a Three-second Timeout on Event Hooks

As specified in the Avoid delays in hook responses document, Okta enforces a three-second timeout on all outbound requests for event and inline hooks. Okta sends one request retry in the event of a timeout or an error response from the external service. Okta returns an HTTP 504 Gateway timeout error if a successful response is not received after the retry.

What prevents the duplicate data issue?

Prevent Event Hook timeouts and duplicate data by configuring the workflow to return an immediate success response.

• Respond immediately to the HTTP request with either a 200 (Success) or 204 (Success no content).
• Use the API Connector: Close card to allow the Workflows engine to asynchronously process the rest of the flow.

To prevent timeout risks, close the HTTP connection as quickly as possible. This can be handled in Workflows using two primary approaches:

• Use the API Connector Close Card: Place this as the first card in the flow. It immediately releases the HTTP connection back to the caller while the Workflows engine continues processing the rest of the flow asynchronously.
• Combine Call Flow Async With Flow Control Return Raw Cards: Trigger the workload asynchronously while maintaining precise control over the initial HTTP response sent back to the client.

Related References

• API Endpoint Flow Timing Out when Called even though the Flow Runs Successfully
• Best practices for building flows