Skip to main content
Your trigger didn’t turn off at random. Gumloop switches a trigger’s status to Off automatically after 3 consecutive failed runs. It’s a safeguard: a trigger that keeps firing into the same error burns credits and piles up failed runs, so Gumloop leaves it off until you fix the cause. This applies to every trigger type: scheduled, app, webhook, and AI-created custom triggers.
When a trigger switches off automatically, Gumloop notifies the owner by email, Slack DM, and in app. Account problems send Reconnect an account, which opens the trigger for repair. Other failed-run notifications link to the most recent failed run. Dismiss the notification once you have handled it.

Why it turned off

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, click the trigger in the Triggers tab of the configuration panel, then click View all under Recent tasks and choose the Failed filter in Task 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:

Turn it back on

  1. Fix the cause first. Turning the trigger back on without fixing it just switches it off again on the next runs.
  2. Open the agent and go to the Triggers tab.
  3. Open the trigger and set Status to On in the Trigger Details header, or choose Activate from the trigger’s ⋮ menu.
Re-enabling resets the failure count. Only failures after you re-enable count toward the next auto-disable, so earlier failures won’t turn it off again on their own. You can turn on your own trigger if Create triggers is Allow. Otherwise ask an Owner or Org Admin to turn it on. Owners and Org Admins can also turn on other people’s triggers. See Who Can Manage Triggers?.
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 isn’t set to stay valid until revoked. Fix the source of the repeated failures, not just the trigger.

Stop it from happening again

  • Keep credentials healthy. Refresh the connector before its access expires. For a shared automation, use a team connector so one person leaving doesn’t 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

Not from the app. Fix the error that keeps failing, or handle it in the agent so the run finishes successfully.
No. The schedule, prompt, and settings stay intact. Re-enabling picks up exactly where it left off.
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, or the creator lost all access to the agent, which removes their triggers. Removing one share does not remove them if another grant still provides access.
If the saved account was removed or its sign-in was rejected, use Connect on the trigger rather than just turning its status on. Sign in again or select another saved account; you do not need to delete and recreate the trigger. Only the owner can reconnect a personal account. For a team account, you need access to it and permission to edit the trigger. See Reconnect a trigger’s account.

Stop a scheduled trigger

Deactivate or delete a trigger yourself.

Who can manage triggers?

Owner and User permissions.

Revoke and reconnect a connector

Fix an expired or disconnected credential.

Agent triggers

How scheduled, app, and webhook triggers work.