cs-icon.svg

Limitations of Automate

  • Automate is a plan-based feature, and the number of executions allowed depends upon the Automate pricing plan that is activated for a particular organization.
  • Organizations that have upgraded to a paid plan will have a soft cap for executions (when reaching this threshold they will be notified by email), and a hard cap that is 5x the number of the soft cap. After the organization hits the hard cap, automations will be temporarily disabled for that month.
  • By default, each organization will be enrolled in the Explorer Plan, which is included at no cost and allows up to 200 executions per month (200 soft cap and 200 hard cap).
  • The maximum number of projects allowed per organization is 50.
  • The maximum number of automations allowed per project is 50.
  • The maximum number of steps allowed per automation is 15.
  • Currently, organization members can only view and edit their own projects.
  • There is no support for nesting within Conditional Path and Repeat Path steps.
  • The Pause and Response action connectors cannot be used within Conditional Path and Repeat Path steps.
  • The maximum number of loops per Repeat Path is 100.
  • For Direct Queue (if automation is not throttled), the rate limit is 5000 executions per minute per organization.
  • You can select up to 10 executions per second from Automate Settings (if an automation is throttled) for a specific automation.
  • If an automation includes a Response connector, Retry Execution will not be available for that automation.
  • Currently, when previewing a JSON payload object within Automate, only the first 3 nodes of an array (such as those used in loops) are displayed in the Design mode. This limitation is intended to optimize performance and ensure efficient data rendering in the browser.
Was this article helpful?
^