erre_ci-event-timeout

[flat ravine]

Hi 👋 I would recommend getting access to the dashboard if you're needing to develop a flow where seeing the Event logs is beneficial to your debugging. One endpoint received that Event twice because we did not receive a response to the first request within our 20-second timeout window. So we interpreted that as the Event not being successfully delivered and queued it to be sent again.

Typically we see that behavior arise whenever there is too heavy of a processing task that triggers before a response is sent to use to acknowledge receipt of the Event.

[zenith hill]

i send a 200 immediatly before i process the event just to avoid this problems

[flat ravine]

I would recommend double checking that code is working the way you intended, the first request we sent did not receive a response within 20 seconds. It's always possible that happened due to a network blip though.

[zenith hill]

ok, i use this code for other clients so the code is correct 😉 (may be...) it is the first time that i have this problem, with the event id can you check the error ? please, just for this time....

evt_1OMt8nHetfxij0wIdtfgzfNL

[flat ravine]

I'm not sure what else you want me to check. I can't see how the code on your server behaved or if it threw any errors, you would need to investigate that. All I can see is that we didn't get a response in time.

erre_ci-event-timeout

[zenith hill]

I misspoke, I don't want you to check my code but since I don't have access to the stripe backend , I was asking if you could verify from your end, the type of error for event id evt_1OMt8nHetfxij0wIdtfgzfNL

[flat ravine]

We didn't receive a response, that was the issue.

[zenith hill]

uhhh strange ok, i m going to double check my end point server...but just to be sure , the second event call was ok ?

[flat ravine]

Yup