Make webhooks more resilient to outages

Our organisation makes quite extensive use of webhooks and the Wrike API to tailor the platform for our needs. This works really well for us and is big plus for Wrike.

One issue that is obvious however is the "three strikes and you're out" feature of webhooks where, if an event can't be delivered on the third try the webhook is marked as inactive and nothing further is sent to it until you manually send an update via Postman to bring it back online.

This means any failure, or scheduled upgrade of equipment, can bring the webhook down and any events that would have been sent until it is re-enabled are lost forever.

It would be better if events were queued for delivery until such time as the webhook is back, ideally with polling to see when it has been re-activated, rather than waiting for the specific API instruction.

I realise this is a relatively niche request, so is unlikely to ever get the number of upvotes required to be considered. However, it would make the webhook+API offering far more resilient and dependable. Previously I have asked for a UI for the webhooks that are sent (https://help.wrike.com/hc/en-us/community/posts/19138803265047-Feature-request-Webhook-UI-for-developers) which was a much bigger ask! Hopefully this stands a better chance of being implemented.