A run produced a plan, and the plan was rejected — maybe deliberately, maybe by a mis-click. Either way the run is now over, and the task is sitting without a delivery. This page covers what rejection did and how to get a working run again.
For what a plan is and the approve/reject decision in full, see Plans and plan approval and Approve or reject a generated plan.
What rejecting a plan does
Rejecting a plan ends the run. The moment a rejection is confirmed, two things happen:
- The run moves to Cancelled. This attempt is over. DIJJI.ai doesn’t revise the plan in place or quietly try again — a rejected run stops for good.
- The rejection reason is posted to the source issue. The reason you gave is added as a comment on the GitHub issue the task came from, alongside the run number, so the feedback lives with the original request.
The good news, if you rejected by mistake: nothing was lost. A plan is rejected before any code is written. No pull request was opened, no branch was touched, and no further credits were spent. The only cost is starting a new run.
I rejected it by accident
There’s no undo for a rejection — the run is Cancelled and won’t come back. But recovering is quick, because rejection happens so early that there’s nothing to unwind.
Go to the task and select Re-run. A fresh run starts, produces a new plan, and brings you back to Awaiting Plan Approval with a new version to review. This time, approve it.
One thing to know: your accidental rejection reason was already posted as a comment on the source issue. You can leave it or delete the comment in GitHub — it doesn’t affect the new run either way.
The plan was rejected on purpose — now what?
If the plan was rejected because it genuinely misread the task, the path forward is the same Re-run, but the rejection reason now does real work. The new run reads the reason from the cancelled run and uses it to produce a better plan.
So before you re-run, it’s worth checking the reason was specific. A vague reason (“not right”) gives the next attempt little to go on; a precise one (“the plan changes the public API — it should only touch the internal helper”) steers it. You can’t edit the reason on a cancelled run, but you can make the next attempt count:
- Re-run, let the new plan appear, and read it against what the last reason asked for.
- If the new plan still misreads the task, reject it again — with a sharper reason — and re-run once more. Each attempt reads the last rejection.
- If the task itself is unclear, fixing the wording of the source GitHub issue before you re-run often helps more than another rejection reason.
Confirm the run is really rejected, not failed
On the run detail page, check the state badge:
- Cancelled — the run was stopped deliberately, including by a plan rejection. This page applies.
- Failed — the run hit an error, not a rejection. See Run states; a failed run is retried, not re-planned.
A cancelled run keeps its plan card in a read-only form — it shows the rejection, who made it, when, and the reason given. That card is your record of what was rejected and why.
Still stuck
If you’ve re-run the task and the new run won’t produce a plan, or it ends without reaching Awaiting Plan Approval — reach out to DIJJI.ai support. Include the project name, the task, and the run number.