This article explains why an API Connector card configured with an Event Hook sends duplicate data to Workflows and why multiple Workflows are triggered for the same event.

• Event Hooks
• Workflows

Workflows receive duplicate data because the Event Hook times out, which triggers a retry (as per design).

As specified in the Avoid delays in hook responses document, all outbound requests for event and inline hooks are subject to a three-second timeout.

In the event of a timeout or an error response from the external service, one request retry is sent. If a successful response is not received after that, an HTTP 400 error is returned with more information about the failure.

In order to avoid these timeouts, respond immediately to the HTTP request with either a 200 (Success) or 204 (Success no content).

Then, the Workflows engine asynchronously processes the rest of the flow. See API Connector: Close.

Related References

• API Endpoint Flow Timing Out when Called even though the Flow Runs Successfully