less than a minute read • Updated an hour ago
Troubleshoot and retry failed webhooks
How to read webhook failure errors, what automatic deactivation means, and how to resend a webhook after fixing the issue.
If a webhook fails after all automatic retry attempts, an entry is added to your store’s error log, and an email is sent to your store’s configured email address(es).
Reading the error log
Each failed webhook entry follows this format:
TITLE (TYPE): ERROR_MESSAGE [HTTP_CODE]
TITLE — the title of the webhook
TYPE — the type of webhook:
json,zapier, orwebflowERROR_MESSAGE — the error message received from the endpoint, trimmed to 500 characters. For the JSON Webhook, this is the body of the response
HTTP_CODE — the HTTP status code of the response
Did the event still complete?
Yes. A failed webhook doesn’t undo the event that triggered it. If it was a transaction webhook, the customer was still charged and payment will still process through your gateway as normal — the failure only means your endpoint didn’t receive (or didn’t successfully process) the notification.
Automatic deactivation of failing webhooks
If a single webhook endpoint fails 12 times in a row — whether from one trigger or from multiple simultaneous triggers for the same resource — the webhook is automatically deactivated, and the store is notified by email. An inactive webhook stops sending payloads to the endpoint, giving you time to fix the underlying issue before reactivating it.
You can reactivate an inactive webhook by editing it in the administration. Reactivating it does not automatically resend anything that would have been triggered while it was inactive — you’ll need to manually refeed those, as described below.
Steps to troubleshoot and refeed a webhook
After refeeding, the system re-attempts delivery for another hour as described above, or until it succeeds.
Notes
If you don’t manage the webhook endpoint that failed, you’ll need to share the specific error with whoever does.