Why did my automation pause?
It failed 5 times in a row, ran more than 30 times in an hour, or you ran out of credits. Fix the cause, then turn it back on.
Alori pauses an automation on its own for one of three reasons: it failed 5 times in a row, it ran more than 30 times in an hour, or your account ran out of credits. It tells whoever set it up, by text or in their chat. Fix the cause, then turn it back on.
Also called: automation stopped, paused, not running, stopped working, automatisation en pause, arrêtée, ne marche plus
Step 1: See why it paused
Open Bots and your bot. Under What I do on my own, a paused automation shows the reason:
Paused: it kept failing: it failed 5 times in a row.
Paused: it ran too often: it ran more than 30 times in an hour, which looks like a loop.
Paused: out of credits: an AI step had no credits left.
In your CRM, Settings › Automations says the same in other words: "Paused: it failed several times in a row", "Paused: it kept setting itself off" or "Paused: out of credits".
Click: Bots › your bot › What I do on my own
Step 2: Fix the cause
It kept failing. Click the automation to open it and read the error under Recent runs. The bot's message says it too: "I paused… it failed 5 times in a row (…)". Tell the bot what to change, like a new channel name or phone number.
It ran too often. It's probably setting itself off: for example, it changes a deal each time a deal changes. Tell the bot what it should do instead.
Out of credits. Add credits.
Step 3: Turn it back on
Flip its switch back on, or ask the bot: "turn it back on". That clears the pause.
Click: What I do on my own › the switch
Good to know
Errors that may pass, like an app that didn't answer, are tried again twice (after 1 minute, then 5 minutes) before they count as a failure.
A scheduled run missed by more than a day is skipped, not sent late.
Click Test it on the bot's card to check your fix right away. See How do I test, pause or delete an automation?
If it doesn't work
It pauses again. Open it, read the newest error under Recent runs, and tell the bot exactly what happened.
"That didn't go. Try again." The switch didn't save. Wait a moment and flip it again.