Manage queues
Prepare batches through MCP and control ready or active work from the dashboard.
A queue organizes work across assigned phones. A worker is a device assigned to that queue. A driver item is a unit of queued input, such as an account or another selected resource.
Open Queues to search, filter by status, and follow progress.
Prepare a queue
Ask your connected assistant to select an exact saved setup, resolve its required inputs, and prepare the devices and items. A useful request is:
Prepare a queue for this exact saved setup. Use only the devices and resource rows I select. Show the item count, worker devices, AI adapter, proxy choice, and any missing requirements. Create a draft and finalize it to Ready when valid. Do not start it until I confirm.
A preview does not create work. A draft can be edited through MCP and finalized to Ready. A combined create-and-start operation begins execution immediately, so use it only when that is your intent.
The browser lists drafts, but their View action is disabled and their details cannot be opened there. Continue draft preparation with your assistant.
Understand queue states
| State | Meaning |
|---|---|
| Draft | Still being prepared; not available for browser detail review |
| Ready | Prepared and waiting for Play/Start |
| Active | Scheduling or executing work |
| Paused | Scheduling is paused; inspect current workers to see whether work is still finishing |
| Completed | Queue processing has completed; inspect the results for failed or retired items |
| Stopped | Terminally stopped; Resume is not available |
Waiting can be caused by device availability, resource capacity, access, or another reported condition. Read the waiting reason before changing the queue.
Control execution
| Control | Effect |
|---|---|
| Play | Starts a Ready queue after Titan rechecks its requirements |
| Soft pause | Pauses new scheduling without itself interrupting work already running |
| Hard pause | Pauses scheduling and interrupts current work |
| Resume | Allows future work again; it does not restore items interrupted by a hard pause |
| Stop | Ends the queue and retires outstanding work; completed history remains |
| Delete queue | Stops current work and removes the queue after the required stop succeeds |
Use the pause menu to choose the intended pause mode. Wait for current status after each action. A delayed response is not a reason to submit the same action repeatedly.
Inspect workers and items
Open a Ready or live queue and use its Workers and Drivers tabs.
Worker cards show the current activity and, when available, a Predicted Next activity. A prediction is not a guarantee. Pausing an individual worker cancels its current item and starts stopping its active run; its device stays assigned, and the queue's overall state is unchanged. Resume that worker when you want it to accept new work.
Driver tables separate failed, unfinished, and completed items. Use Cancel or Re-queue only where offered. Re-queue can perform the work again, so check the previous attempt and any external changes first.
Use My Runs for execution details and Automation troubleshooting for stalled or failed work.