Limits

Limits exist at two levels: what the agent declares and what the space allows. A definition declaring more than the space allows is refused at publishing time.

Declared by the agent

Limit	What it does	Required
Timeout	The run's total deadline. Once exceeded, it ends as expired	Yes
Maximum iterations	The work ceiling for AI steps	Yes
Subagent depth	How far the agent-calls-agent chain may go	No. Default: 3

Each step can also have its own timeout, which has to fit inside the run's timeout.

Cost limit

The product lets you declare a cost ceiling, but it is not yet enforceable: what the engine reports is consumption in tokens, not an amount. While that is the case, this field brakes nothing — and the interface says so, rather than faking a brake.

Trigger rate

Path	Limit
HTTP address	Per address, adjustable. Default: 60 per minute
Manual	Per person: 30 per minute
Re-run	The same as a manual run
Step test	Its own bucket: 60 per minute, per person
Schedule	The schedule's own frequency, plus the concurrency policy

The step test has its own limit on purpose: if it shared the manual run limit, the test button would become the way around it.

Changing the idempotency key does not get around any limit.

Concurrency

Where	Limit
HTTP address	Concurrent runs per address. Default: 5
Schedule	Concurrency policy: do not allow, allow, or replace
Child runs	Up to 50 per run

Size

Item	Ceiling
A run's input	256 KiB
Text produced by joining data	64 KiB
The body of an HTTP call to an address	256 KiB, adjustable per address

Waiting

Situation	Ceiling
Wait step	Up to 30 days
Human approval	No deadline by default; the deadline is optional

How a limit shows up

Limit reached	Outcome
The run's timeout	Run expired
The step's timeout	The step fails; it may retry
Iterations	The AI step fails, limit reached
Depth or recursion	The agent call fails
Fan-out	The "For each item" step fails — it never silently cuts the list
Rate	The trigger is refused with a specific error

Adjusting them

The space's ceilings are adjusted by whoever administers the space. The agent's limits are declared in the agent itself, within those ceilings.

When a space ceiling is lowered, agents already published keep running with what they declared: the change applies to later publications.

Next steps

• Spaces and access
• When something fails
• Execution errors