Workflows - Webhook

Ask for Help
1

Good time of day.

Please tell me how to deal with WEBHOOK delays. How do I create a WAIT FOR CONDITION for conditions?

The problem is that I call the WEBHOOK via the CALL API and pass the ROW ID to the BODY. But the WEBHOOK does not always have time to receive it, since the data has not yet been recorded in the database. The problem gets even worse if you do another SET COLUMN VALUES ROW before the CALL API. It just doesn’t have time to find the data.

I tried to make a LOOP that will be 50 times, doing something empty, but it doesn’t always help. And if you put it 1000 times, then the problem may arise in queues on the WEBHOOK

2

To be clear
1.At the front end: user creates new row by Form screen and on “on submit” action you trying to trig web hook with body of newly created Row ID
2. At the back end:
Glide’s web hook received Row ID in body completely (not always?)
During webhook’s flow execution you trying to query Row ID and mostly it fails, because this Row ID still not present in backend Glide table.
How Glide teams suggests to deal with this?

As a temporary solution i can figure this:

  1. At front end, instead of trigging webhook on “on submit” action, do add row with newly created Row ID to the task table.
  2. At the backend:
    Create workflow which start every minute and go thru task table and trying to proceed with query row ID and when it pass to mark this row as processed or just delete this row from task table.
    Off course it will cost much more updates, but can solve aviating issue
3

Every minute? 1440 UPDATES per day?)))

4

How can I suggest fixing this problem to the GLIDE team. You need to add a condition check function to the LOOP. If the condition is met, then exit the LOOP, otherwise continue to execute.

And of course, make a queue on the WEBHOOK.

In this case, everything will work out perfectly.

1 Like
5

Move to Feature request?
Or ask @DJP for help?

6

What data source are you using? If you use Big Tables it has more guarantees about settling the changes before the web hook is called.

1 Like
7

Yes we was used Glide tables, yes for now i had tested with Big table and issue is gone. But, again and again developing with Big tables slowing down the speed of developing due we must use tons of special tricks to force get needed data from GBT. Actually, most of us - not Darren Murphy and GBT still need some love for Rollups and Lookups. I hope, Santa David will give as this love, may be soon. Dreaming!

3 Likes
8

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