A few platform-wide rules govern what your workspace can do and how much it can run. Understanding them explains why a run might be rejected or a feature might be unavailable.
1. Credits
Running automations consumes credits. Before a run starts, Automize checks that there are enough credits for it:
- If there aren't, the run is rejected with an "insufficient credits" reason – nothing runs and nothing is charged.
- Your remaining balance is shown in the app (for example on the Play panel when you run a process), and the Play button is disabled when you're out.
Top up or review your balance under your billing settings.
2. Plan features
Some capabilities are unlocked by your plan rather than by credits. Cloud automation, for example, is a plan feature: if it isn't included in your plan, the Cloud option is hidden and Cloud runs are blocked. When a plan limit stops an action, Automize shows the reason so you know what to upgrade. Plan features are managed by an administrator.
3. Rate limits
To keep the platform responsive and fair for everyone, some actions are rate-limited – capped at a certain number of requests over a short window. Public endpoints such as webhook triggers are limited this way. If you hit a limit, wait briefly and retry; if you regularly run into one, talk to your administrator about your plan.