# Workflow time limits count only working time

> An agent workflow's time limit now counts only the time its run spends working, holds across the whole run, and is 60 minutes for new workflows.

Oct 27, 2026. Topics: Workflows, Agents, Platform. https://www.generalinput.com/changelog/2026-10-27-run-time-limits-count-working-time

Every agent workflow has a time limit: the most minutes one run may spend before it stops. That limit used to start over whenever a run picked back up, after you answered its question or after it moved to a fresh server during an update, so the number in a workflow's settings said little about how long a run could take. Long chats had a different problem: after an hour of work they ended as if you had pressed Stop. A time limit now counts only the time a run spends working, across the whole run, and new workflows start at 60 minutes.

### How it works

- **Working time only.** Time a run spends waiting for your answer, or waiting in line for a server, never counts toward its limit.
- **One limit per run.** A run that picks back up after a question or an [update](/changelog/2026-10-15-workflow-runs-survive-deploys) gets only the time it has left, and still gets its warning before the end.
- **60 minutes by default.** New agent workflows and app agents start with a 60-minute limit, which you can change in the workflow's settings. Workflows you already have keep the limit they were given.
- **Long chats keep going.** A chat that works past 45 minutes is handed back to the queue at its next step and picks up from there, instead of ending as if you had stopped it.

### Also shipped

- A workflow run handed to a fresh server during an update no longer fails as interrupted when every server is busy.
- A chat whose server crashes is picked back up each time, as long as it keeps making progress, instead of only the first three times.