Hi,
I struggle almost whole day today to make API data polling work.
It is absurd to me how on 2nd biggest automation platform, it is even a thing, not to have something out of the pocket to create in some simple manner polling.
I’ve tried everything including variables and aggregators…
No, if you are using a Commit directive in an error handling route, the scenario will terminate.
That is correct, the module is forced to throw an error to follow the error handling route, which you have not set up yet.
That is because you have no error handling routes from the sleep module.
Please copy my scenario exactly.
For more information, see
Links
Here are some useful links and guides you can use to learn more on how to use the Make platform, apps, and app modules. I found these useful when I was learning Make, and hope they might benefit you too —
Thanks @vendy it might be useful for someone who’s struggling with same problem, that is why I posted the solution.
I kind of understand why you don’t have polling out of the box, because it is a sort of the outdated paradigm in data synchronisation replaced by web-hooks or server-side events or whatever.
But there would definitely are going to be cases, where you need “while” loop to perform some action.
I’ll try come up with some diligently thought module for that.
Are you aware you can use the Make.com integration modules to trigger, and even turn on and off scenarios? I would suggest having a scenario that executes every 5 minutes and checks for your response here. This scenario is turned off, but can be turned on by the “parent” scenario (with whatever data it needs stored in a DataStore). When it successfully reads the data it needs and continues, it can turn itself off (or trigger another scenario which turns off the repeating one).
Using this kind of modularity can also help you separate re-usable parts of your scenarios, and call them from each other. It makes maintenance a little easier.