In normal use you'll never meet these. They're here for the day an agent gets stuck in a loop, so it can't fill your channel with posts or use up your usage overnight while you're away.
One connection can make 60 calls a minute across everything it does. The actions that cost you something have their own hourly counter on top of that:
Per connection, per hour | |
|---|---|
Series renders | 10 |
One-off renders | 10 |
Publishes | 10 |
Disconnecting a channel | 10 |
Layer re-rolls | 20 |
Plan re-rolls | 20 |
Connecting a channel | 5 |
Reconnecting a channel | 5 |
Every other tool that changes something has an hourly cap of its own in the same shape. Your account has one more on top: 20 renders an hour across every agent you've connected, and renders you start yourself in the app don't count towards it. Your plan's limit on renders at once applies to agents too, and asking for one more gets the agent told to wait for a running render to finish.
Renders at once | |
|---|---|
Starter | 1 |
Creator | 2 |
Pro | 4 |
Max | 8 |
When a cap trips, the agent is told how many seconds to wait, and a well-behaved one waits and tries again. The counters behind the table are approximate, so a burst can slip a couple of extra calls through. The two render caps are counted exactly, as each render starts.
The limit that matters most is your usage. Every render is checked before it starts, and one that needs more than you have left is refused. The agent is told there isn't enough usage left, and that a usage pack or a bigger plan covers the gap. If you have usage packs but Extra usage is off, it's told to switch it on or wait for your monthly reset. An agent can't top you up either: ask it to buy usage and it hands you a link to open in your signed-in browser, where you pick the pack and pay yourself. If something looks off, Settings → Authorized agents shows what your agents have been doing, or email [email protected] and a human will read it.