> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gumloop.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Why Did My Trigger Turn Off?

Your trigger did not turn off at random. Gumloop pauses a trigger automatically after **3 consecutive failed runs**. It is a safeguard: a trigger that keeps firing into the same error burns credits and piles up failed runs, so Gumloop turns it off until the cause is fixed.

This applies to every trigger type: scheduled, app, webhook, and AI-created custom triggers.

<Note>
  When a trigger auto-disables, the owner is notified by **email, Slack DM, and in app**. The notification links straight to the most recent failed run, which is the fastest way to see what went wrong. Dismiss it once you have handled it.
</Note>

## Why it turned off

| Reason                        | What happened                                                                                                                                                                                                                                                                     |
| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **3 consecutive failed runs** | The common one. Three failures in a row and the trigger is paused. A single successful run resets the count to zero. A run skipped because the previous run is still going is not a failure and does not count.                                                                   |
| **Runs kept being dropped**   | If your account is at its concurrent-run limit every time the trigger fires, those runs are skipped. After a long streak of skipped runs, the trigger is disabled and the owner gets an email. Usually it means the trigger fires far more often than the agent can finish a run. |
| **No active paid plan**       | Recurring triggers stop running when the owning account no longer has an active paid plan.                                                                                                                                                                                        |
| **Someone turned it off**     | A person deactivated or deleted it, or, if the trigger is **AI Managed**, the agent paused it because you asked it to.                                                                                                                                                            |

## Find the cause

The trigger being off is the symptom. The failed runs tell you the cause.

1. Open the notification and click through to the failed run. Or open the agent and go to its run history.
2. Read the last few failed runs from just before it turned off. The error on those runs is the real reason.

## Common causes and fixes

Ordered by how often they come up:

| Cause                                  | What you see                                                                                                                                         | Fix                                                                                                                                   |
| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| **Expired or disconnected credential** | Runs fail on an integration step with an auth, token, or permission error. OAuth apps like Salesforce, Google, Notion, and Slack are the usual ones. | **Refresh** the connector, then re-enable the trigger. See [Revoke and Reconnect a Connector](/help/connectors/revoke-and-reconnect). |
| **Out of credits or over a usage cap** | Runs fail with a credit or usage limit error.                                                                                                        | Top up credits or raise the cap, then re-enable. While the account is over the cap, runs keep failing.                                |
| **A deleted or renamed resource**      | The channel, folder, database, or record the trigger watches no longer exists, or its permissions changed.                                           | Point the trigger at the current resource, or restore access, then re-enable.                                                         |

## Turn it back on

1. Fix the cause first. Re-enabling without fixing it just disables the trigger again on the next runs.
2. Open the agent and go to **Triggers**.
3. Re-enable the trigger.

Re-enabling **resets the failure count**. Only failures after you re-enable count toward the next auto-disable, so earlier failures will not turn it off again on their own.

You can re-enable a trigger you created. For a trigger someone else set up, you need to be the agent **Owner** or an **Org Admin**. See [Who Can Manage Triggers?](/help/triggers/who-can-manage-triggers).

<Warning>
  If the trigger turns off again right away, the root cause is still there. The classic example is a credential you refresh but that keeps expiring, such as a Salesforce connected app whose refresh token policy is not set to stay valid until revoked. Fix the source of the repeated failures, not just the trigger.
</Warning>

## Stop it from happening again

* **Keep credentials healthy.** Refresh the connector before its access expires. For a shared automation, use a [team connector](/help/connectors/use-team-connectors) so one person leaving does not break it.
* **Keep credits above zero** on the account that owns recurring triggers.
* **Fire only on new data.** If a trigger fires on every poll instead of only on new data, it wastes credits and its runs start getting skipped. Tighten the condition.

## FAQ

<AccordionGroup>
  <Accordion title="Can I raise the 3-failure limit for one trigger?">
    Not from the app. Fix the error that keeps failing, or handle it in the agent so the run finishes successfully.
  </Accordion>

  <Accordion title="Do I lose the trigger's configuration when it auto-disables?">
    No. The schedule, prompt, and settings stay intact. Re-enabling picks up exactly where it left off.
  </Accordion>

  <Accordion title="My trigger disappeared instead of being paused">
    Check whether it was a one-time scheduled trigger. Those delete themselves after they run, success or fail, so a missing one-time trigger ran, it did not fail. Otherwise, someone with access deleted it, and it has to be recreated.
  </Accordion>

  <Accordion title="I refreshed the connector but the trigger still will not run">
    If the connector the trigger was built on was **revoked or deleted**, re-enabling will not fix it. The trigger still points at a credential that no longer exists, and connecting the app again creates a new one rather than restoring the old one. Delete the trigger and create it again on the reconnected account. This is the most common reason a trigger keeps failing after what looks like a clean fix.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Stop a Scheduled Trigger" icon="circle-stop" href="/help/triggers/stop-a-scheduled-trigger">
    Deactivate or delete a trigger yourself.
  </Card>

  <Card title="Who Can Manage Triggers?" icon="user-lock" href="/help/triggers/who-can-manage-triggers">
    Owner, Editor, and Viewer permissions.
  </Card>

  <Card title="Revoke and Reconnect a Connector" icon="rotate" href="/help/connectors/revoke-and-reconnect">
    Fix an expired or disconnected credential.
  </Card>

  <Card title="Agent Triggers" icon="bolt" href="/core-concepts/agent_triggers">
    How scheduled, app, and webhook triggers work.
  </Card>
</CardGroup>