#vipera74

1 messages · Page 1 of 1 (latest)

arctic arrowBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

dusk yacht
#

24 hours should be sufficient, but I'd recommend monitoring in case if the duplicated event is sent beyond this period

fickle sorrel
#

So you would suggest keeping them for longer?

#

I've read that they can be reused by the API after 24 hours

dusk yacht
#

I've read that they can be reused by the API after 24 hours
Where did you read this from? Can you share the doc link?

fickle sorrel
#

Sure, let me find it and get back to you asap

#

My bad. After reviewing all the documentation regarding webhooks and events once again, I could not find this specific information. That may be the reason why it got me confused... it's not true 😄 it seems from the documentation that it's safe to assume that the event ids are statistically universally unique

#

If you could second that, just to be sure, I'd be glad!

dusk yacht
#

It's unlikely the duplicated event will be sent after 24 hours, so it should be safe to keep the event ID in the records for 24 hours. However, if you observe otherwise, I'd recommend extending the retention period

fickle sorrel
#

Alright. Is there a maximum suggested?

dusk yacht
#

I'm afraid we don't have a SLA for this. I'd recommend starting from 24 hours and adjust the retention period accordingly

fickle sorrel
#

No problem at all, thank you for your help and time nonetheless! I will certainly do that, adjusting the time as needed. Thanks!