Skip to main content
Your organization is at one of its live limits, so the request was refused. Nothing was created. The limit frees as soon as one of your running resources ends.
This URL is the type of the error. Match on type, not on message. The message text can change.

When you get it

A resource counts while it runs. It stops counting when it ends, or when it passes its deadline:
  • An execution counts until its workflow timeout, plus 5 minutes.
  • An environment counts until its expiry time.

Response

The status is 429 Too Many Requests. The body follows RFC 9457.
string
required
Always https://docs.asteroid.ai/errors/limit-reached for this problem.
string
required
Live limit reached.
integer
required
429.
string
required
A sentence you can show to a person.
string
The request path that was refused.
string
required
The limit you reached. See When you get it.
integer
required
Resources of this kind running when the request arrived.
integer
required
Your organization’s limit for capability.
integer
The same as status. Kept for older clients.
string
The same text as detail. Kept for older clients.

Handle it

1

Queue the execution instead

For executions, send "onCapacityLimit": "queue". The execution waits as queued and starts by itself, oldest first, when a slot frees. You never see this error. See Queue when capacity is full.
2

Or retry later

Wait for a running execution or environment to end, then send the request again. Back off between attempts.
3

Raise the limit if you hit it often

Limits come from your plan. Contact support to change them.