250 sandbox builds a day
What changed
- 250 sandbox builds a day per developer account, across every application you have created. It was 50.
- A counter of its own. Production builds no longer use up your sandbox builds.
- One app cannot drain the others. A build refused because that app's own sandbox allowance is spent counts against nothing else.
- Refusals name the limit. Every sandbox build refusal says which limit stopped it, its number, and how to get past it.
| Limit | Sandbox, per day | How to get past it |
|---|---|---|
| Person, per credential | 25 | Provision another test user |
| Application | 50, unless raised | Request a higher limit from Usage |
| Developer account | 250 | Email developer@layout.link |
| Credential, every person | 50,000 | Email developer@layout.link |
Every limit resets at midnight UTC. A refused build is not an HTTP error: the order tool answers normally, with no cart and a userMessage that names the limit.
Why it matters
Five times the room for testing, and production traffic can no longer use it up.
What to do
Nothing. To tell a refused build apart, check for the absence of a cart, not the message text. Usage raises one application's allowance; to raise the account limit, email us. See Rate limits and idempotency.
Breaking changes
None.