Circuit breaker on webbooks for a dead API?

Hi there, I have a quick question regarding the way in which your webhooks operate. Creating a webhook for vehicle location updated works perfectly. However, my API (local environment, really), died/was not running for several hours.

Then, on the next day, every webhook event that Motive sent, got a code of 0 which means they were marked as "to be retried". What I did to combat this was to basically call the webhook id, get the retry list and update, but you can imagine how this is not ideal in a prov environmeent.

The next solution was to re-create the webhook with the same secret, disable the old one, and then the webhook (new one) started working again. Of course we are not aiming for several hours of downtime in prod, but I am wondering if this a Motive circuit breaker where a dead API is marked as "dont deliver to anymore" and thus why every code was marked as 0.

If so, I'd appreciate to know this so I can create safeguards in our API.

Thank you!