Queues & Workflows

Queues let you chain multiple bots into a sequential or parallel pipeline. Workflows give you a visual node-and-link editor for more complex routing logic. Both support retry policies, failure handling, and credential environments.

Queues

A Queue is an ordered list of bots. When the queue is triggered (manually or by a trigger), each bot runs in sequence, one after the other, on the assigned runner or runner group.

Creating a queue:

Go to Web Console → Queues → New Queue.
Give the queue a name and select a default runner or runner group.
Add bots in the order you want them to run.
For each item, configure the failure policy and optional retry count.
Set the Asset Environment (Dev / Staging / Prod) for the entire queue.

To run a queue, click Run on the Queue page, or attach it to a Trigger to dispatch it automatically.

Queues can be paused and resumed at any point. When paused, the currently running bot finishes, then the queue waits until you resume it.

Failure Policies

Each queue item has a On Failure policy that controls what happens when that bot exits with an error:

Stop Queue

Default. If the bot fails, the queue stops immediately. Remaining items do not run.

Continue (Parallel)

The queue continues to the next item without waiting for this bot to finish. The failing bot's result does not block the pipeline — useful for independent side tasks like notifications or logging.

Retry Bot

Re-run the failing bot up to N times before applying the Stop Queue policy. Set the retry count on the item.

Note — Continue (Parallel) dispatches the item as a fire-and-forget job. The queue advances to the next item immediately, without waiting for the parallel job to finish. The queue only completes once all parallel jobs have reported back — tracked internally with an async job counter.

Tip — Use Retry Bot for bots that interact with external services that occasionally time out or return transient errors. Start with 2–3 retries and set the bot to add a wait at the start of its script.

Managing Running Queues

While a queue execution is in progress, you can:

Pause — let the current bot finish, then hold.
Resume — continue from where the queue paused.
Cancel — stop the running bot and abandon the queue.

Individual bot runs within a queue can also be paused and resumedvia the Bots page while they're active. The Python process is frozen in memory and resumes exactly where it left off.

Workflows

Workflows give you a visual node editor to connect bots with branching and merging logic. Think of them as queues with a flowchart UI.

Building a workflow:

Go to Web Console → Workflows → New Workflow.
Drag bot nodes onto the canvas and connect them with links.
Each node can target a different runner, group, and asset environment.
Click Run to execute the workflow, or attach it to a Trigger.

Workflow variables

You can pass variables between workflow nodes via environment variables. A node can write a value to a special env var, and a downstream node reads it. Configure variable names in the Workflow editor.

Note — Workflows are suited for complex multi-branch pipelines. For simple sequential runs, Queues are easier to configure and manage.

Queues vs. Workflows — when to use each

Scenario	Recommended
Run Bot A, then Bot B, then Bot C	Queue
Run Bot A; if it fails, skip B and run C	Workflow
Run bots in parallel then wait for all	Queue (Continue Parallel)
Complex branching based on bot output	Workflow
Attach to a cron or email trigger	Either
Retry on transient failures	Queue (Retry Bot policy)