A project works on one run at a time. When you start a task while the project is already busy, it doesn’t get turned away — it joins the project’s queue and starts on its own when the project is free. This page explains how that queue works.
For what tasks and runs are, see Projects, tasks, and runs; to start a run, see Execute a task.
In Queue and Queued
Two labels describe a task that’s lined up, and they mean different things:
- In Queue — the task is waiting its turn behind the active run. You put it here, and you control where it sits in line. A task stays In Queue for as long as the project is busy.
- Queued — the task’s turn has come and it’s just about to run. This is a brief, momentary state as the run gets going; you don’t act on it. A task passes through Queued on its way from In Queue to Running.
In short: In Queue is “waiting in line,” Queued is “next, starting now.”
How a task joins the queue
When you select Run on a task and the project is already working on another run, DIJJI.ai asks Add to queue? — “This project is busy with another run. Add this task to the queue — it will start automatically when the project is free.” Confirm with Add to queue and the task drops to the end of the line.
If the project is free, the task starts straight away and never enters the queue. The queue only forms when work stacks up.
The Queue panel
When a project has tasks waiting, a Queue panel appears above the task list, headed Queue with a count. Each waiting task shows:
- Its position in line, numbered from 1.
- An In Queue label.
- Move up and Move down arrows to reorder it.
- A Remove from queue control (✕) to take it out — removing a task from the queue doesn’t delete it; it just stops it waiting to run.
The queue shows up wherever you’re viewing tasks: as this panel above the List view, and as a Queue column on the Board. Tasks run from the top down — position 1 goes next.
Hold and release the queue
A Stop queue / Start queue toggle sits on the Queue panel. Stop queue holds the whole line in place — the active run finishes, but no waiting task starts after it. Start queue releases it again, and the next task begins. Use Stop queue when you want to pause new work without cancelling anything.
When the queue pauses itself
Sometimes the queue stops on its own and shows an amber banner explaining why. The common reasons:
- A task failed — review the failed task before more run.
- You cancelled a task.
- Insufficient balance — top up to continue. See Credits and billing.
- The daily spending limit was reached — the queue resumes automatically after the daily reset (midnight UTC), or you can resume it manually. See Balances, spending limits, and time.
- Your project’s code is out of date — sync it before more tasks run (see Keep your project in sync).
- A sync failed, or an unexpected error stopped the queue.
The banner names the reason and, where it’s something you fix, points you at the fix. Once the cause is cleared, select Start queue to release the line again — except the daily-limit pause, which lifts itself after the reset.
How it fits together
A project runs one task at a time. Everything else you start while it’s busy waits In Queue, in the order you choose, and each one moves to Queued and then Running as the project frees up — unless you’ve stopped the queue, or it paused itself for one of the reasons above. To start a task and meet the Add to queue? prompt firsthand, see Execute a task.