Limits

Every number on this page is one the runtime actually enforces. Where something is measured rather than enforced, it is not here, because a measurement published as a limit is a promise nobody made.

How long a run may take

A run has a wall-clock deadline: at least half an hour, and longer for a Playbook with more steps, at twelve minutes per step. Whichever is larger is the deadline.

A single attempt at one step waits at most ten minutes before it is considered stalled.

Retries

A step that fails is retried up to three times, with a delay that grows between attempts. Retries happen inside the run rather than by starting it again, so a retried run is still one run.

A retried step is billed for its final attempt only. The wasted attempts are absorbed rather than charged to you.

Truncation

Three ceilings, all at thirty thousand characters:

• what a reference file contributes to the step that reads it,
• what a tool call returns into a step,
• how much of a fetched web page is kept before it is read.

A step that calls tools in a loop stops after eight rounds, whatever it is doing.

Uploads

Twenty-five megabytes, which is both the upload ceiling and the size at which a reference file can still be replaced through the app. A file larger than about a quarter of a megabyte is stored and used but not previewed or edited in place.

Only text-shaped files are read into a step. Anything else is described to the step by name, type and size rather than by its contents.

Money

A top-up is at least five pounds. A per-run price on a published Service has no minimum: zero is valid.

What is not limited

There is no request rate limit. Nothing in YAMO caps how often you or an agent may call it, so if you are planning around one, plan around its absence instead.

Delivered email

A finished document is sent in the body of the completion email up to a generous ceiling, and a longer one is trimmed with a line saying that it was. The full version is always in the run folder.