Bug causing all webhooks to fail with retry of 0

AppSheet AppSheet Q&A
, ,
1

image
image780×831 78 KB

Recently every webhook task that I’ve got with a retry of 0 has silently started to fail.

  • Its failing because 0 apparently isn’t allowed for the retry attempts anymore

Would be nice if there was an actual error produced by these webhook errors.

  • Showing green when the webhook is red is really confusing and makes for a terrible user experience

Others are reporting as well

6 Likes
2

Due to being force to use a retry number of 1, everything is now sending duplicates because the first one takes too long to come back.

  • This is an AppSheet API webhook to another app
  • Since the AppSheet API waits for all the events to finish before it returns, the system isn’t waiting long enough before it retries.

image
image1010×1330 97.9 KB

  • Read from the bottom up
  • Looking closely, you can see the duplicates are coming roughly 60 seconds after the first try.

I need one of two solutions: :folded_hands:

  1. Allow 0 for the retry

    • This will allow me to build systems that integrate webhooks that take longer than whatever window you’ve established (looks like around 60 seconds).

  2. Allow us to set the retry window

    • This way I can establish how long it should wait for the response
    • This would allow for really tight tuning of the system

Or… best of both worlds!

image
image345×146 12.9 KB

As it is, this is causing a bunch of duplicates because of how long some apps take to respond. (And rebuilding these apps so that they work differently is… not something that’s on the short list.)

3 Likes
3

My problem is slightly different from yours,
but there’s definitely a problem with the AppSheet webhook.
Currently, the Max number of retries on failure setting can’t be set to 0.
However, if it’s set to anything other than 0,
the webhook will start to experience other issues.
However, in Monitor, only successful executions are visible. In reality,
AppSheet keeps experiencing incorrect retries.
Setting the Max number of retries on failure setting to 1 results in duplicate operations in the backend.

1 Like
4

Appsheet engineer here - I apologize for the trouble. This was an unintended regression, stemming from what should have been invisible changes to the underlying code when a webhook is invoked, and not a deliberate change in behavior. We’ve identified the cause and have prepared a fix, which is planned to be deployed on Monday (9/8).

4 Likes
5

Thank you, Trevor!

2 Likes
6

The fix went live on 9/9 (sorry again for the delay)

3 Likes
7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.