Why an automation was switched off

If one of your automations suddenly stops running, this article explains why InfraNest turned it off and how to turn it back on safely.

Overview

• InfraNest automatically switches off a rule when running it again would only fail again — it won't keep failing silently in the background.
• There are two reasons this happens: a missing permission on a connected account, or repeated failures.
• Both show a clear status on the rule, and both are fixable.

Fix "the connected account is missing a permission"

Some actions ask another service to make a change for you — for example, Set Cloudflare development mode or Purge Cloudflare cache. That service only allows the change if the account you connected was given the right permission.

If it wasn't, the service refuses the request. Trying again won't help, so InfraNest stops the rule the first time this happens and sends you a notification, rather than letting it fail over and over.

The banner on the rule 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 Integrations and open the account the rule uses.
2. Reconnect the account, granting the permission named in the banner. Reconnecting is genuinely necessary — an existing connection can't be widened, so refreshing or re-testing it won't add the permission.
3. Go back to the automation and switch it back on.

NoteThis especially affects accounts connected before 1 August 2026. The Cloudflare actions were added then, so connections made earlier were never asked for the two permissions they need.

Fix "Switched off after repeated failures"

This status means the rule failed five times in a row. That usually means something it depends on has changed — a server that no longer exists, a webhook address that no longer answers, or a value that's no longer valid.

1. Open the automation.
2. Check its recent runs to see which step failed and what the error said.
3. Correct the problem (update the step, fix the value, reconnect the account, etc.).
4. Switch the rule back on.

Tips

WarningSwitching a rule back on without fixing the underlying cause will simply get it switched off again the next time it runs.

• A step marked continue on error never causes the automation to switch off — the run carries on past it, and that step's error is explained in the run history.
• Every automatic switch-off is recorded in your Audit Log, so you can review what happened and when.