Pipeline states

What this means

Every pipeline shows a state badge on the detail page and in the pipelines list. The state tells you what the agents are doing right now, whether the pipeline is finished, and whether it needs your attention.

States fall into four groups:

Active - work is happening. The badge animates.
Waiting - paused on a person. The badge is amber.
Blocked - admin attention - paused on an admin configuration change. The badge is orange.
Terminal - finished. The badge is green (done), red (failed), or muted (cancelled).

A pipeline in an active, waiting, or blocked state polls every few seconds. Terminal states stop polling.

Where you see it

The pipeline detail page header.
The pipelines list, next to each row.
The dashboard's recent pipelines list.
The browser tab title - Bilbis prefixes the title with a glyph that mirrors the state, so you can tell at a glance whether a backgrounded pipeline finished, failed, or needs you.

States

States below are listed in roughly the order a successful pipeline goes through them.

Active states

The pipeline is making progress. Polling continues every few seconds.

Badge	Meaning
Initializing	The pipeline is starting up.
Routing	The Repo Router picks a repo (in Let Bilbis pick mode) and decides the plan.
Planning	The Work Planner decomposes the task into file-level steps before coding starts. Skipped on short single-repo tasks.
Coding	The Implementation Agent is writing code.
Testing	The agent runs the project's local tests.
Visual check	The agent compares results against a Figma reference, when one was attached.
Pushing	The agent commits the work and pushes a branch.
CI	The agent waits for your CI provider to run checks.
CI fixing	CI failed. The agent reads the failing job log and pushes a fix.
Reviewing	The Review Agent reads the diff and writes review comments.
Addressing review	The Implementation Agent addresses the Review Agent's comments.
Merging	The pipeline is merging the MR or PR.

Waiting states

The pipeline is paused on something only a person can resolve. Polling continues. The badge is amber.

Badge	Meaning
Needs your input	The agents asked a question. Open the pipeline and reply in the Clarifications tab. See Awaiting clarification.
Awaiting approval	The MR or PR is open and the pipeline is waiting for a human approval before it merges. The header shows an Approve & Merge button and a countdown to auto-merge if your product has it enabled. If the provider rejected the merge attempt, the header also surfaces a Merge blocked banner with a friendly reason and an Open MR/PR link.
Paused — ticket on hold	The Jira ticket moved into a configured hold status, so Bilbis paused the pipeline. It resumes automatically as soon as the ticket leaves all hold statuses. Configure hold statuses in Settings → Integrations → Jira.

Blocked - admin attention

A pipeline can pause until an admin updates configuration. Polling continues. The badge is orange.

Badge	Meaning
Configure Jira fields	A Jira workflow transition that Bilbis tried to make required fields Bilbis didn't supply (for example a start date on Code Review). The pipeline pauses until an admin fills in Transition field mappings in Settings → Integrations → Jira (or on a per-product Jira override). The pipeline resumes after the admin updates the mapping and retriggers.

The latest reason - which fields Jira asked for, or which hold status the ticket moved to - is on the Timeline tab as a callout on the most recent transition.

Queued

The repo already has another pipeline running. New pipelines on the same repo wait their turn. The badge shows a clock icon. Priority controls the order - see Priority in Create a pipeline.

Terminal states

The pipeline has stopped. Polling ends here.

Badge	Meaning
Done	Success. The MR is merged (or the dry run finished).
Failed	The pipeline ran out of options and stopped. Open the Diagnostics tab on the detail page for the reason. See Pipeline failed.
Cancelled	An admin cancelled the pipeline, or a 48-hour timeout fired on a pending clarification.

Approval flow

When a pipeline reaches Awaiting approval:

The header shows a yellow callout with a countdown.
A logged-in admin can click Approve & Merge on the page itself.
An approval can also come from the merge request page, the pull request page, or a Jira reply (depending on how your product is configured).
A scheduled job picks up approvals within about 60 seconds and flips the state to Merging.

If your product has auto-merge turned off and the approval window expires, the pipeline stays parked until someone approves it. The header callout switches to red copy that says "Approval window expired - still parked".

If the provider's last merge attempt failed (CI not green, conflicts, missing approval, draft status, branch protection, and so on), a separate red Merge blocked banner sits below the approval banner. It quotes the friendly reason, the raw provider status (gitlab:discussions_not_resolved, github:behind, http_<code>, etc.), and offers an Open MR/PR link straight to the source. A scheduled job retries the merge every ten minutes - you don't need to retrigger it.

Cancelling a pipeline

While the pipeline is in any non-terminal state, the header shows a Cancel button. Cancelling stops further state transitions. Work that's already running inside the agent's container will finish on its own; Bilbis just stops moving the pipeline forward.

Problems and fixes

Problem	What to check
The pipeline is stuck in Routing for a long time.	Check Diagnostics on the detail page. If the Repo Router can't decide between repos, the pipeline parks in Awaiting clarification with a question.
The pipeline keeps going CI → CI fixing → CI in a loop.	The agent is iterating on a real CI failure. If it doesn't converge, see CI still failing.
The pipeline is in Awaiting approval longer than expected.	Check whether your product has auto-merge on and what the approval timeout is. Approvals from Jira or the MR/PR can take up to 60 seconds to reflect.
Merge blocked banner is showing under Awaiting approval.	The provider rejected the last merge attempt. Read the friendly reason on the banner and fix it at the source (resolve threads, get an approver, undraft the MR/PR, rebase). Bilbis retries every ten minutes - no manual retrigger needed.
The pipeline shows Paused — ticket on hold.	Move the Jira ticket out of the hold statuses listed in Settings → Integrations → Jira → Hold statuses. Bilbis resumes within the next webhook poll.
The pipeline shows Configure Jira fields.	An admin must add the required fields to Transition field mappings in Settings → Integrations → Jira (or on the per-product override). The latest required field names are on the Timeline tab callout.
The pipeline is in Awaiting clarification but I never asked anything.	The agents asked you a question. Open the Clarifications tab on the detail page.
The pipeline reached Failed but I want to retry.	Bilbis doesn't retry automatically. Open a new pipeline with the same task description, or use a saved template.

Create a pipeline - every form field explained.
Review results - read the detail page tabs.
Troubleshooting - recovery guide.

On this page