Catching Shopify orders your webhook workflow never received

@Shafique_Mumtaz both are already how it works: the health check is its own workflow and only reads (webhookSubscriptions plus a GET on each URL), so it never touches order processing. The alert lists the expected topics next to what it found, e.g. “No subscription for ORDERS_PAID pointing at your-n8n-host”, with the fix underneath (deactivate and reactivate the trigger workflow, then run the missed-orders check for the gap). Thanks for the input throughout this thread, the guide is better for it.

Thanks for confirming that, @TrenoxaHQ — good to hear the health check stays read-only and separate from order processing, and that the alert names the missing topic and the exact subscription URL. That makes the fix much less guesswork than a generic “webhook failed” message.

One small addition worth considering: if a subscription is missing, it can also help to log the last successful check timestamp alongside the alert, so you can tell at a glance whether the gap started with a deactivation, a URL change, or just a quiet period with no orders. Thanks again for folding the thread’s feedback into the guide — the deactivation/reactivation step plus the missed-orders check for the gap is a clear recovery path.

Good idea, @Shafique_Mumtaz. I’ll add the last OK check time to the alert in the next version, so you can see when the gap started.

Thanks for picking that up, @TrenoxaHQ — that timestamp will make the alert much easier to triage. One small detail that could help alongside it: if the alert also shows how long the gap is compared with the usual check interval (for example, “last OK 3 hours ago, checks run hourly”), it is immediately clear whether this is just a quiet stretch or a real break. Looking forward to trying the next version — happy to test it against the deactivation and reactivation flow you described.