Timeout settings

Symphony timeout applies to the entire Symphony execution. It defines the maximum total time allowed for the Symphony to complete, from start to finish. All activities within the Symphony must be completed within the set time frame.

By default, a Symphony timeout is one hour. You can change the timeout settings in the Security & Settings tab.

Flow timeout applies to individual activities, such as a flow, API call, or RPA state, within the Symphony. It defines the maximum time allowed for a specific activity to complete. You can change the timeout settings in the General tab of the activity properties.

• Symphony timeout is configured in the Security & Settings menu. It acts as a global cap. If the Symphony exceeds this time, it is forcefully terminated.

  Use these best practices for the Symphony timeout configuration:

  • Set based on the longest expected execution path.
  • Ensure the sum of all activity timeouts (plus buffer) fits within the timeout limit.
    Note: The timeout limit ranges from one minute to thirty days.
• Flow timeout is configured in the General tab in an activity properties panel.
  Tip: Click on an activity on the canvas to open the activity properties panel.
  If the activity exceeds this time, it is marked as failed, and the Symphony follows the defined error path, if any.

  Use these best practices for the Flow timeout configuration:

  • Tailor timeouts to the expected duration of each activity.
  • Avoid setting flow timeouts longer than the Symphony timeout to prevent validation errors.
  • Use error handling to manage failures gracefully and allow the Symphony to follow alternative paths without unnecessary delays.