Scenario was rejected: No free slot was acquired

:bullseye: What is your goal?

Fix this Problem.

:thinking: What is the problem & what have you tried?

We’re experiencing an issue where triggering the scenario with “Run once” returns the error message: “Scenario was rejected: No free slot was acquired.” In some cases, it also appears that automatic trigger events disappear from the Make queue.

:clipboard: Error messages or input/output bundles

Scenario was rejected: No free slot was acquired

:camera_with_flash: Screenshots (scenario flow, module settings, errors)

This usually happens when Make can’t start the scenario because all execution slots are busy.

I’d check whether there are long-running runs, too many webhook calls coming in at once, or sequential processing turned on. If queue items are disappearing too, it sounds more like a backlog/platform-side execution issue than something wrong in the scenario itself.

Are you on us2.make.com? There was an outage earlier.

For more information, see Make Status - Executions on the us2.make.com not working

2 Likes