Skip to article

Where Do You Find Out an AI Agent's Run Failed or Stopped?

Where Gumloop shows that an AI agent's run failed, stopped or is waiting on you, and what to do about the reasons a trigger switches Off.

By Jacqueline V. TwillieNovember 10, 20266 min readGuide
Quick answer

When three consecutive failed runs switch a trigger Off, Gumloop tells the trigger's owner by email, Slack DM and in the app, with a link to the latest failed run. A run waiting on approval shows under Approval Required, and Task history has a Failed filter. The pages checked describe no other alert for a failed run.

The email says a trigger on your AI agent switched itself Off, and a Slack DM says the same.

The owner gets the notice, and the linked pages don't say whether the owner is always the creator Trigger Details names. Ask whoever built it where their notices land.

What can stop a run, and where does each stop show?

A trigger switches itself Off after three consecutive failed runs. The owner is notified by email, Slack DM and in the app, and the notice links to the latest failed run. A single successful run resets the count, and a run skipped because the previous run is still going isn't a failure and doesn't count.

Trigger Details shows the reason beside Off when Gumloop knows one, such as Too many failed runs, Monthly run limit reached or Account needs reconnecting. The help page lists more reasons, and some list a fix of their own.

For Account needs reconnecting, refresh the connector, or connect the account again if someone removed it, then switch the trigger on. If the connector was revoked or deleted, switching on won't help, so delete the trigger and create it again on the reconnected account.

Monthly run limit reached comes with no fix on the page, and you may ask Gumloop's support what applies to your account.

Runs skipped again and again at your account's concurrent-run limit end with the trigger disabled and an email to the owner. The help page ties that to firing far more often than a run can finish.

Recurring triggers also stop when the owning account has no active paid plan. Removing a member from the organization switches off every trigger they created, and removing them from a team switches off their triggers on that team's AI agents.

A person may have deactivated or deleted one, and a one-time trigger deletes itself after it runs, worked or not.

A run waiting on approval is paused and hasn't failed. Pending approvals show under the Approval Required filter on the Tasks page, in the notification bell, a Slack DM or the chat thread. The linked pages don't describe a scheduled run reaching a card, but a trigger's prompt is processed as if typed in chat and a gated call pauses, so expect a gated send to wait.

Model Fallback, in the Settings tab, retries and then switches to a model from a different provider when the primary is unavailable, and it's on by default. Override Auto Fallback lets you pick fallback models yourself. Auto falls back to its baseline model when it can't route. Beyond those and the notices above, the linked pages describe no general fallback, retry or alert system.

Checked on 2026-11-11 against Gumloop's help page on why a trigger turns off, its AI agent triggers page, its approvals page, its AI agent builder page and its AI models page.

How do you build the failure watch in Gumloop?

  1. 01

    Filter the Triggers page to Off and read each reason.

    Open Gumloop and select Triggers in the left sidebar. Set the Status filter to Off, open each trigger, read the reason beside Off and note who created it. Checked on 2026-11-10 against Gumloop's page on AI agent triggers.

  2. 02

    Read the failed runs before you switch anything on.

    Click through from the notice, or open the AI agent, click the trigger in the Triggers tab, choose View all under Recent tasks and pick the Failed filter in Task history. The error on the last few failed runs is the real reason, usually an expired credential, no credits left or a deleted or renamed resource. Fix it, then set Status to On in the Trigger Details header, which resets the failure count. If Create triggers isn't Allow for you, ask an Owner or Org Admin, who can also turn on other people's triggers. Checked on 2026-11-10 against Gumloop's help page on why a trigger turns off.

  3. 03

    Open Approval Required for runs that are waiting on you.

    Select Tasks in the left sidebar and set the Approval Required filter, or open the notification bell. Approve or reject from the bell, or open the task from the Tasks page. Checked on 2026-11-10 against Gumloop's page on approvals.

  4. 04

    Ask for a trigger report and compare it with the Triggers page.

    Paste the message below into that AI agent's chat. How Do I Schedule an AI Agent to Run on Its Own? covers sending a prompt on a timer. Then compare the reply with the Triggers page and, on the Tasks page, set Source to Triggered by Schedule and Date to the same window. If the reply says "I can't see that" for every trigger, read the Triggers page and the filtered Tasks page instead. Checked on 2026-11-11 against Gumloop's AI agent builder page and its AI agent triggers page.

I am an ambassador for Gumloop. Code VIBE20 takes 20% off your first month.

What message do you send to get the trigger report?

The linked pages list no tool that reads a trigger's status or run outcomes. What the AI agent can report follows from three lines: it can list its own triggers; with Edit Own Instructions and AI Managed on, it can pause, resume or reword them, and each change needs your approval; and Search Past Tasks retrieves earlier tasks. The message asks for "I can't see that" in place of a guess, and bars any change.

Copy and fill in
Today is [TODAY'S DATE]. Report on the triggers of this AI agent, and only report. For each trigger give its name, its status (On or Off), the reason shown beside Off if you can see one, and the outcome of the latest runs you can see since [DATE OF MY LAST CHECK]: finished, failed, skipped, or waiting for my approval. Then list the tasks of yours that are waiting for my approval. Write "I can't see that" for anything you can't see, and don't guess. Change nothing: don't pause, switch on, edit, create or delete a trigger, and don't approve or reject anything.

Does the report agree with the Triggers page?

Set each status in the reply against the Triggers page. Where they disagree, go with what the Triggers page shows.

For a trigger that sits Off with no failed run in its Task history, check the other reasons above: a limit, a plan, a removed creator or a person.

When one kind of line keeps coming back as "I can't see that", cut it from the message. To turn a stopped trigger back on, use How Do I Pause an AI Agent While I'm Away and Turn It Back On?.

Frequently asked questions

Who gets told when a trigger switches itself Off?

After three failed runs in a row, the owner, by email, Slack DM and in the app; after a long streak of skipped runs, by email.

Does Gumloop retry a run that failed?

In the linked pages, a retry is described only for an unavailable model, under Model Fallback in the Settings tab, and none for a failed run.

Why is a trigger gone instead of switched Off?

A one-time trigger deletes itself after it runs, and a person with access can delete a trigger.

More on Ownership for Non-Technical Managers