Why an automation was switched off

If one of your automations stopped running on its own, this article explains why — and how to turn it back on safely.

#Overview

• InfraNest automatically switches off an automation when running it again would just fail again, instead of letting it fail silently over and over.
• There are two reasons this happens: a connected account is missing a permission, or the automation failed repeatedly.
• Both are fixable, and the automation itself tells you which reason applies.

#Fix: the connected account is missing a permission

Some actions — like Set Cloudflare development mode or Purge Cloudflare cache — ask another service to make a change for you. That service only allows it if the account you connected was given the right permission. If it wasn't, the service refuses, and InfraNest switches the automation off the first time this happens and sends you a notification.

The banner on the automation names the exact permission needed — for example Zone Settings:Edit — spelled the way the provider spells it, so you can find it on their screen.

1. Go to Go to Integrations and open the account the automation uses.
2. Reconnect the account, granting the permission the banner named.
3. Go back to the automation and switch it back on.

NoteReconnecting is genuinely necessary — an existing connection can't be widened, so refreshing or re-testing it won't add the missing permission.

This mostly affects accounts connected before 1 August 2026: the Cloudflare actions were added on that date, and connections made earlier were never asked for the two permissions they need.

#Fix: switched off after repeated failures

If you see Switched off after repeated failures, the automation failed five times in a row. This usually means something it depends on has changed — a server that no longer exists, a webhook address that no longer answers, a value that's no longer valid.

1. Open the automation.
2. Check its Runs to see which step failed and what the error said.
3. Correct the problem the error points to.
4. Switch the automation back on.

#Tips

TipMark a step Always carry on if it shouldn't be able to switch off the whole automation — the run will continue past it, and the step's error still shows up in the run history.

#Troubleshooting

• Switching an automation back on without fixing the underlying cause will simply switch it off again the next time it runs.
• Every automatic switch-off is recorded in your Audit Log, so you can check when and why it happened.