Skip to main content
About the Resource Center

Task and state editor actions

The Architect task editor provides several tools that help you create a sequence of actions to make up a task. These task actions are available from the Architect Toolbox. A unique icon appears for each action, so you can easily identify it in the toolbox, task editor, and design area. The actions in the Architect Toolbox vary depending on your Genesys Cloud license plan. For more information about the task editor and the Toolbox, see the Suggested content.

Maximum number of actions in a flow

The maximum number of actions Architect runs per flow invocation is 10,000. If the system exceeds that number, the flow enters error handling. The default error handling is a disconnect; however flow authors can configure alternative actions, such as a Transfer to ACD, Jump to Menu, or Jump to Reusable Task.

If you choose to go to a menu or reusable task, Architect automatically increases the action by an extra 1,000 actions. This process allows you to configure an alternative path for the error handling. If you exceed the additional maximum, Architect performs a silent disconnect.

Architect considers each of the following processes as an action that counts toward the 10,000 limit:

  • Each time you enter a menu
  • Each menu action
  • Each task action
Note: Unlike menus, entering a task does not count as an executable action.

Collapse or expand an action

Within the task or state editor, and in task or state preview mode, you can collapse or expand actions. This feature is helpful when you want to hide lengthy pieces of logic that can make the task or state difficult to navigate.

To help familiarize yourself with actions in the task editor, review the following pages: