Just wondering if anyone seeing a delay in webhooks?
Hey Daryl!
Can I get some more info on your subscriptions to investigate this further? I’ll shoot you a DM so you can drop in your App ID, myshopify URL and other information^
Following up from DMs here - looks like there’s an issue on your side.
Re: What are we doing to help deal with this issue: We did launch Next Gen Events (or simply, Events), that allow you to define what triggers an Event, what payload it carries and run filters on it! Read more about it here: About Events and webhooks
About the burst of incoming webhooks - with Events, we’ll work on batching them early next year - more on that when we have something to share, but it is on the roadmap ![]()
Good! I was making some major adjustments to our app and thinking, “This has GOT to be killing Shopify’s infrastructure too…” Good to know you guys are doing something about it.
Thanks, Harshdeep. I’ve looked further into Events, and while they appear useful, webhooks remain better suited to our use case because orders need to stay synchronized with Shopify across a broad range of changes.
It’s good to hear that batching is on the roadmap - it’s very much needed. As this incident demonstrated, Shopify can generate an extremely large volume of webhook deliveries for a single merchant. Even with queues and scalable workers, a sudden burst of that size can create a significant processing backlog.
I’d also like to suggest an addition to webhook payload configuration: exclude_fields.
Currently, include_fields requires apps to maintain a potentially large list of every field they need. For order synchronization, we generally need most of the payload but may want to exclude a relatively small number of large or unnecessary fields. An exclusion list would be simpler to maintain and less likely to omit newly introduced fields accidentally.
Please consider passing this feature request to the webhooks team.
Cheers!
Events will solve this, you can pass the query of fields you want.
Thanks, Luke. Events would address the payload size, but they introduce additional complexity and require a significant migration to a new payload structure.
They also still require maintaining a complete query of every field needed. Events are currently in dev preview and webhooks remain recommended for production, I still think exclude_fields would be a valuable addition for existing webhook integrations.
I don’t believe any more changes will be made to classic webhooks with the introduction of Events.