Executing a task starts a run — one attempt at the work the task describes. This page covers starting that run. For where tasks come from in the first place, see Where tasks come from; for what a run does once it’s underway, see Run states.
Find the Run button
You can start a run from two places:
- The Tasks page. Open your project, select Tasks, and find the task’s row. The action button sits at the right of the row.
- The task’s own page. Open the task. The action button sits in the top-right of the page header.
The button is labelled Run for a task that has never been run — one in the Pending state. For a task that previously Failed or was Cancelled, the same button reads Re-run and starts a fresh attempt.
A task that is Queued, Running, or Completed shows no Run button. A queued or running task is already underway; a completed task has nothing left to do.
A Pending task that you haven’t run yet also offers a Delete action, which removes it before it has any run history. See Delete or archive a task for deleting and archiving.
Start the run
Select Run (or Re-run). There is no confirmation dialog — the run starts as soon as the checks below pass.
Before the run begins, DIJJI.ai checks two things:
- Your balance. Starting a task requires a minimum balance of $10.00. If your balance is below it, DIJJI.ai blocks the run and shows an insufficient-balance message with your current balance and a shortcut to top up. Add credit, then select Run again. See Credits and billing.
- Other active runs. A project works on one run at a time. If another task in the same project is already running, DIJJI.ai asks Add to queue? rather than starting a second run. Confirm to drop the task into the project’s queue — it appears in the Queue panel above the task list and starts automatically when the running task finishes. Cancel the dialog if you’d rather not queue it. See The task queue for how the queue works.
One more thing can interrupt the start: if your code has changed outside DIJJI.ai since it last looked, you’re asked to sync first before the run begins — see Keep your project in sync.
When the checks pass, the run starts. Starting from the Tasks page takes you to the task’s own page so you can follow the run; starting from the task page keeps you there and the page updates in place.
What happens next
The task moves from Pending to Queued, then to Running as the run takes hold.
A run’s first work is to read the task and produce a plan — the proposed work, before any code is written. While it does this, the task shows a Planning label.
When the plan is ready, the run pauses at Awaiting Plan Approval and waits for you. Nothing else happens until you approve or reject it — a paused run holds its place indefinitely. See Plans and plan approval for what the plan looks like and what each choice does.
Follow the run
The task’s page shows the run as it progresses:
- Current run — a link to the run’s own detail page, where you can follow it step by step.
- Run history — every run this task has had, newest first, each with its status, duration, and cost.
- Pipeline stages — once a run is underway, where it stands in each stage of your pipeline.
To stop a run that’s already going, use the Cancel button next to Run — see Cancel a running task. For every state a run can pass through, see Run states.