A narrated tour, so turn your sound on. Ivy, a support coworker, groups 200 tickets by theme with a team of helpers, then keeps the run to use again.
What it does
Some jobs aren’t hard, they’re just big. Two hundred support tickets to group by theme. Twenty companies to research before Thursday. A year of meeting notes to boil down. Your coworker starts by writing a plan: the phases the job breaks into. Then it hands the work to temporary helpers. Each one takes a slice, works on it alone, and reports back. Your coworker pulls their reports into one answer, and the helpers are gone when the job is done. These run-only helpers aren’t your coworker’s custom helpers, the named specialists you set up yourself. A run can put those to work too.Who has it now
Nobody, for now. A run puts a whole team of helpers to work, so it costs far more than an ordinary session, and coworkers are kept from starting one. There’s no switch for it: the Capabilities tab no longer lists Dynamic workflows.
The warning sits on the row itself, so the switch never reads as on while nothing happens.
What a run looked like
Each run had its own card in the conversation, and sessions from before keep them. Here’s the one from Ivy, a support coworker, partway through grouping 200 tickets by theme.
Ivy's ticket-themes run partway through. All eight Read helpers are done, and the Check helpers are working through the themes.
The plan comes first
Helpers fill in live
Stop one that's off track
One answer at the end
Letting a run use your apps
A run’s helpers couldn’t touch your connected apps unless the plan asked for them. The one exception was a custom helper with no tool list, which could still do what your permission rules already allowed without asking. Ivy’s plan names Slack, because its last step posts the report to #support-leads. When a plan named an app, you were asked once, before anything ran. The plan appeared on the card once you approved.
One question for the whole run. There's no Always allow, because every run asks for itself.
- Approve let any of the run’s helpers, up to 30, use Slack without asking again. The permission ended with the run, and the card keeps a line saying Using Slack — you approved this for this run.
- There was no Always allow. A standing rule would have approved the apps of every future run, so each run asked on its own.
- A “never” rule still won. Approving a run couldn’t override a permission rule that says Never. Anything else that needed your yes was refused, and the helper said so in its report.
- Decline, and nothing had run, so nothing was lost. Your coworker could rework the plan without the app.
Long runs
A big run didn’t have to finish in one go. After about ten minutes of work it paused, then picked up again on its own straight away.
Ivy's run pauses at 14 done, then starts its next stretch on its own. Finished helpers aren't run again.
Too big for one turn — continuing on the next one. Finished agents are replayed, not re-run.In plain terms: helpers already working finished first, and finished helpers weren’t run or paid for again. The next stretch appeared in the conversation as Started on its own.
Saved dynamic workflows
A completed run’s card used to offer Make repeatable, to keep a run that turned out well. Its tooltip read “Saves this run as a dynamic workflow, then adds it to Workflows with a trigger that runs it.” A coworker’s run cards no longer offer it, and the app refuses it if it is asked anyway: the workflow it builds hands the run to a coworker, so it could never run. A card made repeatable before still links to its workflow. What it made before is kept, but your coworker can’t run a saved dynamic workflow for now. The slash menu in a coworker’s session no longer lists them, and a workflow or a schedule that asks a coworker to run one doesn’t get that work done.
Make repeatable appears only on a run that completed. Ivy's ticket-themes run is ready to keep.
- A saved dynamic workflow. It’s kept in your coworker’s own files, in the
.workflows/folder of its Files tab, where you can read it. - A separate workflow, in the session’s agent. It isn’t the dynamic workflow itself. It has a Start trigger, then one step that asks Ivy to run ticket-themes. For now, Ivy can’t do what that step asks.

The workflow that Make repeatable builds: a Start trigger, then one step that hands the ticket-themes job to Ivy.
Under the hood
The plan was a short script, built from a handful of building blocks:agent, parallel, pipeline, phase, log, budget and args. To read a saved one part by part, see Dynamic workflow scripts.
Good to know
Common questions
Can my coworker run a dynamic workflow?
Can my coworker run a dynamic workflow?
What happened to the dynamic workflows I saved?
What happened to the dynamic workflows I saved?
.workflows/, and the workflows that Make repeatable built stay in Workflows. Your coworker can’t run a saved one for now, so a workflow step that asks it to doesn’t get that work done.Why did a dynamic workflow cost more than a session?
Why did a dynamic workflow cost more than a session?
Could a dynamic workflow post to Slack or use my other apps?
Could a dynamic workflow post to Slack or use my other apps?
