Use case: our company gets after hours requirements for x dump trucks to respond and be in place on very short notice.
We have a dispatch web form that triggers the Make.com scenario and sends mission specific details (location, qty, in place time, etc) in the payload to our scenario. No problem.
To avoid waking everyone, we assign drivers to ‘group 1’ thru ‘group n’.
Group 1 drivers receive an sms with mission details.
Then, a 5 minute scenario delay begins immediately immediately after the last sms is sent. Group 1 members then have 5 mins to accept the load, or decline/ignore.
If none from Group1 accept, the Make scenario looks up ‘Group 2’ and repeats the same steps, starting a second 5 minute delay timer while awaiting a taker.
The intention, ideally, is that a driver accepts the job and clicks a parameterized url in the sms that initiates a few actions. The first action is the challenge:
The challenge: once the job has been accepted we would like to STOP the timer, and send no more sms requests. Wake as few drivers as possible.
The problem: we cannot stop a running delay timer. The scenario stop endpoint ‘turns off’ the scenario, but does not actually ‘stop’ the running scenario (ie, halt the timer and all remaining modules).
Can anyone suggest a work-around, or let me know if I’m not choosing the correct Make.com api command.
Thanks!
POST/scenarios/{scenarioId}/stopscenarios:write
Deactivates and stops the specified scenario if the scenario is running.