Webhook delivery issues

Symptoms

Your webhook endpoint is not receiving events, deliveries are failing, or events are arriving with unexpected behaviour.

Check the delivery log

Go to Settings → Integrations and find your webhook endpoint. Each delivery record shows:

• Status — delivered, pending (retry scheduled), or failed (all retries exhausted).
• HTTP response code— The status code your endpoint returned.
• Attempt count— Which attempt this was (up to 3).
• Error message— A description of what went wrong, if applicable.

Common failure causes

Your endpoint returned a non-2xx status

Tideflow considers any HTTP 200–299 response a success. Anything else triggers a retry. Check your endpoint logs to see why it returned an error.

Request timed out

Tideflow waits up to 8 seconds for your endpoint to respond. If your endpoint takes longer, the delivery is marked as failed for that attempt and retried. Make sure your endpoint responds quickly — do heavy processing asynchronously after sending the response.

Endpoint URL resolves to a private IP

Tideflow blocks deliveries to private, loopback, and link-local IP addresses as a security measure. Your webhook endpoint must be reachable at a public IP address.

Endpoint is disabled

If the webhook endpoint is marked as inactive in your settings, deliveries are skipped. Make sure the endpoint is enabled.

Retry behaviour

Failed deliveries are retried up to three times:

1. First retry after approximately 1 minute.
2. Second retry after approximately 5 minutes.
3. If the third attempt fails, the delivery is marked as failed permanently.

Duplicate deliveries

Each delivery includes an X-Tideflow-Delivery-Id header with a unique identifier. If your endpoint might receive the same event more than once (for example, during retries), use this ID to deduplicate on your side.

No events being sent at all

• Confirm you have at least one event type selected for the endpoint.
• Confirm your plan includes the webhooks feature.
• Use the test button to send a sample event and verify your endpoint receives it.

Signature verification failing

If you are verifying the X-Tideflow-Signature header and it does not match, check that you are using the correct signing secret and computing the HMAC over the exact format {timestamp}.{raw body}. See webhook authentication and delivery for details.

Still not working

Contact support@tideflow.au with the delivery ID and endpoint URL so the team can help investigate.