Limits and errors
Requests
Section titled “Requests”Each request has a ~8,000-token budget covering input, questions and options. It’s an estimate, not the model’s tokenizer. Oversized requests get a 413 before any run or allowance is used.
| Plan | Concurrent runs | Attempts / minute |
|---|---|---|
| Starter | 2 | 30 |
| Pro | 5 | 120 |
Failed attempts count toward these limits but not allowance. Runs past the execution deadline fail and release their allowance.
Workflow storage
Section titled “Workflow storage”| Account | Workflows | Total versions | Versions / workflow | Stored size |
|---|---|---|---|---|
| No paid plan | 5 | 20 | 10 | 1 MiB |
| Starter | 25 | 500 | 100 | 16 MiB |
| Pro | 100 | 2,000 | 200 | 64 MiB |
Source is capped at 64 KiB per version and 256 KiB compiled. Old versions count. Downgrading or cancelling doesn’t delete workflows.
Handle errors
Section titled “Handle errors”| Status | Meaning |
|---|---|
| 401 | Missing, expired or revoked credentials. |
| 402 | No paid plan. Check banh billing status. |
| 403 | No access to this account, or wrong credential type. |
| 409 | Conflicting billing change or storage cap reached. |
| 413 | Request or deployment too large. |
| 429 | Rate, concurrency or allowance limit. Honor Retry-After. |
| 503 | Temporary capacity or provider issue. Honor Retry-After. |
| 504 | Run timed out. No allowance used. |
If the managed provider keeps failing, Cloud briefly pauses new attempts; wait for the retry delay. Calls aren’t exactly-once, so check history after a timeout before retrying.