What happens if a webhook misses an event because the server was down?

Let’s say I have a webhook listening for Stripe payment events and I’m updating my server exactly during the time of a purchase.

What happens?
And how to prevent missing events?

Information on your n8n setup

  • n8n version: 1.52.2
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker
  • Operating system: Ubuntu 22.04
1 Like

Hi @gmsalomao2

Usually there will be a retry mechanism from the Stripe end. Meaning if the webhook req is failed. The service will retry the same request after some interval.

1 Like

Hi @gmsalomao2

As @mcnaveen Said there is usually a retry on the other end, but of course that doesn’t solve everything. For example if you webhook is offline too long the retry will not keep on trying for ever.
You can use a service like hookdeck to catch all webhooks and send them to your n8n instance. This way you can always retry from hookdeck if something went wrong on your n8n webhook and it is offline for some time.
Of course you can also beef up your own server infra with webhook workers and loadbalancers, but that is often a bit overkill.

3 Likes

Those are great alternatives. Thanks!

And for services that also have API, I could request periodically for the latest X events and check if they have already been processed.

So we have 3 or 4 different solutions for tha same problem. Topic closed :raised_hands:
Thanks guys!

2 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.