# Failing triggers now pause instead of disabling workflows

> Poll triggers now retry transient errors and judge failures by HTTP status. When one gives up, only that trigger pauses and the workflow stays on.

Apr 30, 2026. Topics: Workflows, Integrations, Platform. https://www.generalinput.com/changelog/2026-04-30-failing-triggers-pause-not-disable

Poll triggers check a service on a schedule and start a run for each new item. When polling broke, we used to disable the whole workflow after three consecutive failures, whatever the cause, so a provider outage could switch off an automation its other triggers were still feeding. As of April 30, a failing trigger pauses only itself.

### How it works

- **Retries in place.** Network errors and timeouts get up to three attempts within a check, and an authentication error retries with a freshly loaded credential in case the token rotated.
- **Judged by status code.** Lost access (401, 403) or a deleted resource (404, 410) pauses the trigger after one failed check. Server errors are tolerated for 25 consecutive checks, other client errors for 3. A rate limit never pauses a trigger.
- **Only the trigger pauses.** The workflow stays enabled, its other triggers keep firing, and you get a notification naming the trigger and the reason. Editing the workflow after fixing the cause turns it back on.
- **A shorter lookback.** Checks look back one hour instead of 24.

### New triggers

[Google Sheets](/apps/google-sheets) row updates, [Airtable](/apps/airtable) records, [Jira](/apps/jira) issues, [DocuSign](/apps/docusign) envelopes, Ashby candidates, Ramp transactions, [Asana](/apps/asana) tasks, and PandaDoc documents.