Stytch webhooks have no ordering guarantees, treat them as a pull signal

TL;DR

Instead treat the event as a signal: for example on direct.member.update, call the Stytch API for that member ID and update your system from the GET response, so you always work with current data even when events arrive out of order. Only use the payload directly for fields you do not store.

Steps

1. On receiving a webhook event, do not write the payload fields directly into your database. Instead treat the event as a signal: for example on direct.member.update, call the Stytch API for that member ID and update your system from the GET response, so you always work with current data even when events arrive out of order. Only use the payload directly for fields you do not store. If events stop arriving, check the Dashboard Message Attempts tab, your endpoint may have been auto-disabled after 5 days of failed deliveries, re-enable it from the webhook dashboard.

When to use

You are seeing this: On receiving a webhook event, do not write the payload fields directly into your database. Use this skill when you run into "Stytch webhooks have no ordering guarantees, treat them as a pull signal".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Edge cases

• Also note Svix automatically disables an endpoint if every delivery attempt fails for 5 days.

Source: Official docs (Webhooks): documents a gotcha that trips agents syncing Stytch data. Stytch webhooks do not inherently offer ordering guarantees, because of retries, network variability, and optimizing for reliability over strict ordering. Writing the event payload straight into your own database can leave stale data when events arrive out of order. The docs recommend using the webhook as a signal to pull Stytch instead. Also note Svix automatically disables an endpoint if every delivery attempt fails for 5 days.

Verified resolution: On receiving a webhook event, do not write the payload fields directly into your database. Instead treat the event as a signal: for example on direct.member.update, call the Stytch API for that member ID and update your system from the GET response, so you always work with current data even when events arrive out of order. Only use the payload directly for fields you do not store. If events stop arriving, check the Dashboard Message Attempts tab, your endpoint may have been auto-disabled after 5 days of failed deliveries, re-enable it from the webhook dashboard.

Source URL: https://stytch.com/docs/resources/workspace-management/webhooks