# Triggers and workflows wait out connected app outages

> When an app you connected goes down, triggers keep checking and catch up, outages stop counting against your workflows, and you hear when it's down and back.

Oct 18, 2026. Topics: Workflows, Integrations. https://www.generalinput.com/changelog/2026-10-18-workflows-wait-out-app-outages

When an app you connected goes down for days, nothing on your side is broken. Until now, a long outage could still pause your triggers, fail your runs, and count those failures against your workflows. Triggers and workflows now wait it out and pick up once the app answers again.

### How it works

- **Triggers stay on.** A trigger whose app stops answering keeps checking, backing off to every half hour as the outage goes on, or longer if the app asks us to wait. It shows "Waiting for" the app instead of "Trigger disabled".
- **Triggers catch up.** When the app is back, most triggers look back to their last successful check, up to a week, so records created meanwhile still start your workflow.
- **Outages don't count against you.** A run whose connection can't renew its sign-in because the app is down doesn't fail: if a webhook or a new record started it, it waits up to three days for the app, and a scheduled run skips that time. A run that fails because an app is down never counts toward turning a workflow off.
- **One email each way.** After an app has been unreachable for an hour, the connection's owner gets one email saying how many workflows use it, and another when it answers again.
- **Paused triggers say why.** A trigger paused because an app rejected its connection or settings now says so and stays paused until you retry it, then catches up the same way.

### Also shipped

- A connection shows when its app isn't responding, and Sync now says when a check failed.
- Connecting an app we have to reach before its sign-in page opens, like Bullhorn, says it isn't responding instead of showing a network error.