Open manan30 opened 3 months ago
We have something coming for you in several weeks. Stay tuned :)
We have something coming for you in several weeks. Stay tuned :)
Perfect, excited about it. Thank you!
Bumping. I am running into this issue myself, it works reliably in localdev but it just doesn't seem to catch in production. Any news or guidance on this issue would be greatly appreciated. We just started building with inngest and I would hate to have to work around this issue if we continue.
Describe the bug
Let's say I have
eventA
andeventB
andeventB
needs to wait foreventA
to complete. Here is how both events are implementedNow the issue is if I do something like this, send both the events one after the other immediately
eventB
never receiveseventA
and it always ends up timing out.But if I add a small timeout between
eventB
andeventA
, something likethen
eventB
does indeed wait foreventA
.I think this might be a race condition but I am not sure if that is intended behavior
Expected behavior
I was hoping the order in which events were issued was deterministic and would not run into race conditions