Usage limits for automations

A few default usage limits are set for automations for each organisation.
As automations are still in beta phase, these limits might be subject to modification.
Maximum number of scenarios
A limit is set on the number of scenarios in PAUSED or ACTIVE states. The default is 100 for each organisation. This limit is checked upon POST /v1/scenarios requests, i.e. when creating scenarios. When the limit is reached the request will hit a 403 HTTP reply.
Maximum number of active scenarios
A limit is set on the number of scenarios with ACTIVE status. The default is 20 for each organisation. This limit is checked upon PUT /v1/scenarios/:scenario_id request with ACTIVE status, i.e. when activating scenarios. When the limit is reached the request will hit a 403 HTTP reply.
Maximum number of nodes per scenario
A limit is set on the number of scenarios in PAUSED or ACTIVE states. The default is 20 for each scenario. This limit is checked upon PUT /v1/scenarios/:scenario_id request with ACTIVE status, i.e. when activating scenarios. When the limit is reached the request will hit a 403 HTTP reply.
Limits related to wait nodes
There are two limit related to wait nodes:
Maximum number of wait nodes in active scenarios. The default is 20 for each organisation. This limit is checked upon PUT /v1/scenarios/:scenario_id request with ACTIVE status, i.e. when activating scenarios. When the limit is reached the request will hit a 403 HTTP reply.
Indicative maximum number of user points awaken per wait node per hour. The Service Level Objective is 50 000. If over 50 000 users will go through your wait node hourly, some users might not be awaken in a timely fashion.
Get in touch with your mediarithmics contact if you need to set higher limits for your organisation.

Last modified 1yr ago