avia wilf

[scarlet briar]

Hi there 👋 you're correct that the behavior is different between the modes. Test mode will retry three times over a couple hours, whereas live mode will retry for up to 72 hours using an exponential backoff approach. I don't have insights into specifics about when those retries are sent, and if that is consistent in test mode.

I hadn't heard of a difference in retry timing based on the status code included in the response, but will look to see if I can find anything more about that.

Sorry, I'm not readily finding anything more specific. Is there an overarching question or goal that is driving these questions that I can try to help address?

[smoky sable]

thank you!

I'm asking b/c I've noticed a difference bwtween returning 406 and 500, and I wanted to understand if that's for a certain reason or not

but if there's no difference, than maybe this difference that I saw was a coincidence or maybe there is another logic there

[scarlet briar]

Gotcha, I'm not aware of a difference, but that doesn't mean there isn't one. If you have some examples I can take a closer look, but if you're seeing that behavior consistently then it may be how things are expected to work.

[smoky sable]

actually I have examples:)

can't tell if it's consistent though

which details do you need? event ids? account id?

[scarlet briar]

Event IDs

[smoky sable]

example for 500 response-
evt_3MyZWDFdCE6n8elI1Y4l0jE1
example for 406 response- evt_3MyaRGFdCE6n8elI1k0EVPyX
for the 406, I retried manually, but it showed that it will retry after 1 hour

[scarlet briar]

Interesting, I haven't seen this before, and will check with my team to see if anyone is aware of expected behavior around this.

[smoky sable]

actually, now I see other cases with 500 response where the first retry was after 1 hour, and not immediately.
evt_3Mxo6dFdCE6n8elI0GSDBf20
so maybe there are specific cases (perhaps regardless of the status code) where the retry is immediate.

[smoky sable]

thank you toby!

[scarlet briar]

Apologies for the delay. Checked with my team and they also aren't aware of any specific pattern.