A Workflow Can Now Be Given More Than Twenty Minutes
August 20, 2026 · InfraScout Team
An agentic workflow running in sync mode had twenty minutes of wall-clock time, and that was the same twenty minutes for every workflow in every tenant.
Some genuinely need more. A thorough health check across several database hosts can outrun twenty minutes on step count alone, and it would end on the deadline with nothing available to raise but the turn budget — which was not what it was running out of.
Max runtime, beside the turn budget
Max runtime (min) now sits in the Limits section of the workflow form. Leave it unset for the twenty-minute default; raise it up to two hours on the workflow that needs it.
The two budgets end a run for different reasons, and it is worth knowing which one you hit. A run that exhausted its turn budget was working. A run that hit the runtime cap was more likely waiting — on a slow host, a long query, or an asynchronous job it is polling.
The budget is fixed when the run fires
A run's effective budget is stamped onto it at the moment it starts, and everything downstream reads that one value.
That matters because InfraScout has a background pass that recovers runs orphaned by a lost server instance, and for a sync run its only signal is age. Its grace window is now computed per run from that run's own budget — so a workflow allowed 45 minutes is not judged against a window sized for twenty, and a workflow that sets no override keeps today's tighter recovery window rather than inheriting whatever your longest-running workflow was given.
A workflow edited or deleted while a run is in flight also cannot move that run's cutoff.
A fix for the enable toggle
Worth reading if you use the toggle on the workflow list, because it was silently resetting settings.
The toggle sent a whole-workflow update, and any field missing from that update was reset. Three were missing — with the result that toggling a sync workflow flipped it to batch mode and dropped its schedules. If you have ever toggled a workflow and found it behaving differently afterwards, that is why.
It is fixed, and fixed completely rather than by adding the one field this release needed, since the next omission would have reset the new budget too. Worth a glance at the execution mode and schedules on any workflow you have toggled recently.
See Agentic Workflows for the Limits section.
Questions or feedback? Reach us at info@infrascout.cloud.