Skip to content

April

In April 2026, the BotCity Orchestrator introduces the Task Timeout feature, which allows setting a maximum processing time per automation. When this limit is reached, the task automatically assumes the status Timeout, indicating that processing exceeded the expected deadline.

Task Timeout

Timeout is an execution control feature that allows defining a maximum time a task can remain in processing. If this limit is exceeded, the task automatically assumes the status Timeout.

Screenshot of the BotCity Orchestrator, in the Tasks menu, showing the different possible states of a task: Waiting, Running, Timeout, Finished, Failed, Partially finished and Canceled. Each state is represented by a corresponding colored icon.

Configuration in the Automation

Timeout is configured in the Execution Policy tab of each automation.

Available fields:

Field Type Description
Enable timeout in this automation Toggle Enables or disables the timeout for the automation
Expected timeout Dropdown + Numeric Sets the maximum time in Minutes, Hours or Days

Configuration rules:

  • Timeout is enabled by default in all new automations
  • Default time: 1,440 minutes (24 hours)
  • Minimum allowed time: 1 minute
  • Maximum allowed time: 1,440 minutes (1 day)
  • The time is counted from the moment the task starts processing — not from creation or time in queue

Behavior when changing Timeout

The Timeout change only applies to tasks created after the modification. Existing tasks retain the behavior defined at the time of their creation.

Tasks

A new status now exists in the task lifecycle.

The task listing displays the new status Timeout in the State column.

When this status appears: on the task that reached the maximum configured processing time without finishing.

Possible transitions: a task in Timeout can still transition to the status Finished, Partially Finished or Error, if processing ends after the limit is reached.

Insights

In BotCity Insights, the new Timeout status is also reflected in the tasks report.

Runner

  • The Runner indicates the start of the process to the BotCity Orchestrator
  • In Tasks, the processing time monitoring starts and triggers the status change when the established limit is reached
  • The status change happens automatically, without requiring any manual action from the user