Your run has stopped. The run detail page shows it isn’t failed and isn’t finished — it’s just sitting there. If the state reads Waiting for Gate, the run is doing exactly what it should: a stage has a gate, and the run can’t advance until the gate’s condition is met.
A gate isn’t a malfunction. It’s a checkpoint you placed on the stage, and it’s waiting on you.
For a full walk-through of clearing a gate, see Resume a run that’s waiting on a gate. This page is the quick diagnosis.
Confirm it’s actually a gate
Open the run detail page and read the status badge near the top:
- Waiting for Gate — the run is held at a gate. This page applies; keep reading.
- Waiting for Payment, Waiting for Answer, or Awaiting Plan Approval — the run is paused for a different reason. See Run states for which page you need.
- Running — the run isn’t stuck at all; give it a moment.
The run is waiting for a pull request to merge
The most common case is a stage waiting for a human merge — one with Auto-merge PR off. When such a stage finishes its work, DIJJI.ai opens a pull request against the stage’s branch, and the run holds there until that pull request is merged.
Nothing in DIJJI.ai advances the run for you. The merge is the action that clears the gate, and it happens in GitHub, not here.
Find and merge the pull request
On the run detail page, expand the card for the stopped stage. Inside it:
- A Pull Request link opens the pull request DIJJI.ai created. That pull request is the stage’s delivery.
- A Waiting for PR merge notice confirms the run is paused until you merge it.
Follow the link, review the pull request the way you’d review a teammate’s, and merge it on GitHub when you’re satisfied. If it isn’t right, don’t merge — leave the run where it is, or cancel it to end the attempt.
It merged, but the run still looks stuck
Two things to check:
- Give it a moment. DIJJI.ai learns about the merge from GitHub, so there’s a short delay. Refresh the run detail page if it still shows the old state.
- Force the run past the gate. If the merge went through but the page still shows the stage holding, a Force Next Stage button at the top of the run detail page pushes the run on — select it and confirm Force next stage?. The same button can bypass a gate you haven’t satisfied yet, so use it knowingly. (When a stage is held on its E2E tests or on deploy confirmation rather than a merge, the stage card carries its own Skip E2E or Force Advance control instead — see Trigger E2E tests manually and Deploy confirmation and the deploy wait.)
Still nothing after the merge
If the pull request is merged, you’ve waited a few minutes, and Force Next Stage either isn’t there or didn’t help — reach out to DIJJI.ai support. Include the project name, the task, and the run number.