You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 11, 2024. It is now read-only.
I want to process webhooks in an idempotent way. Shopify provides us with X-Shopify-Webhook-Id headers. But these get lost in the webhook process function.
It would be great to have access to the webhook ID in my handlers.
Type
New feature
Changes to existing features
Motivation
What inspired this feature request? What problems were you facing?
I want to process webhooks in an asynchronous way, using background workers. For this, I want to use the webhook ID as the background Job ID.
Checklist
I have described this feature request in a way that is actionable (if possible)
The text was updated successfully, but these errors were encountered:
Overview
I want to process webhooks in an idempotent way. Shopify provides us with
X-Shopify-Webhook-Id
headers. But these get lost in the webhook process function.It would be great to have access to the webhook ID in my handlers.
Type
Motivation
I want to process webhooks in an asynchronous way, using background workers. For this, I want to use the webhook ID as the background Job ID.
Checklist
The text was updated successfully, but these errors were encountered: