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
Hey folks, I'm new to inngest and loving the product so far. Currently, I am having difficulties with getting the idempotency key to work. I might be missing something regarding the functionality.
The behavior I am expecting is, when there's a send event, if the id field is set, it will only run a single send call for a given particular id and drop the other send events.
I'm on nextjs, and have this function below using the same const idempotencyKey, testing on local development stack, with local inngest running, called literally one after the other.
I expect this to trigger only once but I see all 3 events succeeding, creating 3 calendar invites. Would love to understand if I'm not using idempotency in the intended way, or running into an inngest issue!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey folks, I'm new to inngest and loving the product so far. Currently, I am having difficulties with getting the idempotency key to work. I might be missing something regarding the functionality.
The behavior I am expecting is, when there's a send event, if the id field is set, it will only run a single send call for a given particular id and drop the other send events.
I'm on nextjs, and have this function below using the same const idempotencyKey, testing on local development stack, with local inngest running, called literally one after the other.
I expect this to trigger only once but I see all 3 events succeeding, creating 3 calendar invites. Would love to understand if I'm not using idempotency in the intended way, or running into an inngest issue!
Beta Was this translation helpful? Give feedback.
All reactions