What is your goal?Process the queue from a webhook trigger
What is the problem & what have you tried?The scenario runs every 6 hours. It should process the queue from a webhook trigger. But it runs only once, processing only the first task in the queue.
I deactivated the scenario and pushed “process old data” but again it processes only the first in queue (1 of 47).
Where is my mistake?
Thank you for any help
Stefan
Create public scenario pageHello @Stefan_Wagner,
Welcome to the community!
You have configured your scenario to run according to a schedule.
Schedule settings
Run scenario: from At regular intervalsto Immediately
Learn more about scenario scheduling:
Hope it helps! If this solves your issue, please mark the reply as Solution → it will help others find solutions to similar problems.
Have a nice day,
Michal
Hi Michal,
Thank you very much for your fast response.
Does that mean with this scenario I cannot use scheduling?
Hello,
Scheduling is designed to work with polling triggers.
When using webhooks (which are instant triggers), the scenario should run every time the webhook is triggered.
You can learn more about triggers in Make.com here:
Is there any reason why you wanted to have your scenario scheduled and triggered instantly by webhook?
Have a nice day,
Michal
Hello Michal,
Thank you very much for the explanation.
You ask why I not want to have your scenario scheduled and triggered instantly by webhook? As far as I understood, I can save credits when the scenario processes only once a day. Isn’t that correct? Soon I will have to upgrade but still then I would not like to spend more money than necessary.
Best regards
Stefan
Hello Stefan,
Not exactly- it depends on how your data is processed.
Each webhook request is a separate execution with its own set of data.
If your scenario takes 10 operations to complete, then each webhook call will consume those 10 operations- but your data is processed instantly.
With a polling trigger (scheduled run), the scenario runs once and can process multiple items in one execution. This canreduce the number of operations, especially if the trigger returns multiple bundles at once.
However, this comes with a trade-off- your data won’t be processed immediately, only when the schedule runs.
But in your case it won’t change anything- 1 webhook call = 1 set of data to be processed.
So in short:
It really depends on your use case and how many items your trigger can return in a single run. You can learn more here:
Have a nice day,
Michal
