Timeouts and Limits

canvas playbooks and components share the same automation limits and timeout model use this topic when you need to know how many actions you can add, how long a run can execute, or what you can configure in the ui versus the platform choose your path i want to… go to know whether there is a maximum number of actions action count limits /#action count limits understand playbook or component run timeouts playbook and component run timeouts /#playbook and component run timeouts understand individual action timeouts action timeouts /#action timeouts see related structural limits (loops, nesting, data size) related structural limits /#related structural limits change timeout values how timeouts are configured /#how timeouts are configured action count limits turbine does not enforce a fixed maximum number of actions on a canvas playbook or component you can add as many actions as your workflow requires large playbooks with many actions can affect editor performance and run duration split complex workflows into reusable components or sub playbooks when practical see swimlane top tips system performance / /swimlane%20top%20tips%20 %20system%20performance md the canvas editor keeps an undo/redo history of up to 30 changes this limit applies only to editor history, not to how many actions a saved playbook or component can contain playbook and component run timeouts a playbook run or component run is the full execution from the entrypoint through all connected actions timeouts apply at this level separately from individual action timeouts default behavior when you do not set a custom timeout value in the playbook or component definition, the platform applies these defaults setting default maximum total run time from start 4 hours 24 hours inactivity extension per period of job activity 1 hour — how this works in practice when a run starts, turbine sets an initial timeout window based on platform defaults as actions execute, the run timeout extends by up to 1 hour from the last job activity the run cannot exceed 4 hours total from the start time unless you set a higher value in the playbook or component definition (up to the platform maximum of 24 hours ) components invoked from a playbook use the same run timeout model when they execute custom playbook or component timeout the playbook and component manifest supports a top level timeout field you can set a human readable duration (for example, 10 minutes , 2 hours ) or a value in milliseconds a value of 0 or an unset field uses platform defaults a custom value is capped at the platform maximum of 24 hours the canvas editor does not expose a playbook level or component level timeout field to set a custom run timeout, update the playbook or component yaml source through the api or an export/edit workflow see how timeouts are configured /#how timeouts are configured action timeouts each action in a playbook or component runs as a job job timeouts are separate from the overall playbook or component run timeout action type default timeout maximum timeout connector actions and most native actions 15 minutes 15 minutes python script actions 1 minute 1 minute sub playbook or component invocation inherits playbook run timeout (default 4 hours, max 24 hours) same as playbook run action retries automatically stop after 15 minutes from the first retry attempt this duration is fixed and aligns with the action job timeout see retries / /retries md individual actions support a timeout field in the manifest (human readable or milliseconds) the canvas editor does not expose a general action timeout control for most action types connector and native actions use the 15 minute platform default unless overridden in the manifest related structural limits these limits are not a cap on total action count, but they constrain how you structure playbooks and components on the canvas limit playbooks components loop nesting depth 5 levels 5 levels component or sub playbook nesting depth 10 levels 10 levels sub playbook or component stack during execution 10 levels 10 levels while loop maximum iterations 5,000 5,000 parallel loop maximum concurrency 5 5 action input and output size 20 mib per action 20 mib per action component name length — 50 characters maximum component description length — 255 characters maximum for loop details, see using the loop native action / /using%20the%20loop%20native%20action md for component naming limits, see components / /building%20blocks/components md how timeouts are configured what you want to change canvas ui playbook or component yaml / api platform configuration (operations) playbook or component run timeout not available set top level timeout in manifest engine playbook timeout , engine playbook max timeout individual action timeout not available for most actions set timeout on the action in manifest engine job timeout , engine job max timeout action retries additional options on the action retryuntil in manifest — platform configuration changes affect all tenants on that deployment coordinate with your swimlane administrator before changing engine timeout environment variables see also how to create a playbook getting%20started/how%20to%20create%20a%20playbook mdplaybooks overview getting%20started/playbooks%20overview\ mdcomponents / /building%20blocks/components mdretries / /retries mdswimlane top tips system performance / /swimlane%20top%20tips%20 %20system%20performance md