Add a "Retry now" button to force webhooks in "Retry" status
If the webhook listener goes offline, the webhook server will try to send the data with increasing delays up to 24 hours where it will stop.
The issue is that if our listener crashes during an extended period of time, we might have to wait for an extra long period of time before it is retried.
Adding a "Retry now" button would allow devs/admins to restore the webhook to their "OK" status much earlier (ie. as soon as the listener has been fixed).
Anonymous
shared this idea
-
Rowan Thorley commented
I just asked for this too, it's soo bloody annoying.
-
The current webhook system will continue trying webhook requests with decreasing frequency. This is extremely annoying, if I wish to test recieving webhooks, but not leave the server running all the time during app development, I have to wait 15mins for it to validate once I restart the server. If I'm fixing bugs or accidentally introduce a bug, I have to wait 15 mins for xero to try sending the webhook request. Perhaps a limit on api requests to stop it being spammed and a button to send webhooks immediately or intent to recieve at any time so that it doesn't waste soo much time.