No config found for repo

What this means

The pipeline failed at or near dispatch with a reason like "No config found for repo my-repo" on the Diagnostics tab. The repo is registered in your product, but the pipeline dispatcher can't find a configuration entry for it.

This is a known backend gap. The frontend creates the repo correctly, but the dispatcher's config resolver and the database table the resolver reads are out of sync. There is no fix you can apply from the docs site or the app - the resolution is on the backend team.

When to use this page

A pipeline ended in Failed within seconds of dispatch.
The failure reason mentions "No config found for repo" with the repo name in the message.
The repo definitely exists in the product (you can see it on the product detail page).
A previous pipeline on the same repo also failed with the same reason.

If your pipeline failed for a different reason, see Pipeline failed.

What's happening underneath

When you create a repo in Products, the frontend writes the repo into the database. The pipeline dispatcher, however, reads its configuration from a separate path - historically a YAML file checked in at deploy time. The dispatcher's resolver has not yet been switched to the database, so it tells the pipeline "I don't know about this repo" even though the database does.

A pipeline that hits this fails immediately, before any agent gets a chance to do work.

Workarounds

There is no clean workaround on the frontend. A few things that may help while the backend is fixed:

Try	What it does	Why it might help
Use a repo that has been working.	Routes the task to a repo whose config the resolver already knows about.	Sidesteps the problem for one task.
Re-create the repo entry in Products.	Forces another database write.	Sometimes nudges a stale resolver cache. Not guaranteed.
Wait.	Backend deploys may include a config refresh.	The fix lands eventually.
Contact your Bilbis operator.	They can apply backend-side fixes.	The only durable resolution.

The pipeline is not retriable from the UI in a way that bypasses this. Re-dispatching the same task to the same repo will hit the same failure.

How to confirm it's this issue

Open the pipeline detail page.
Click Diagnostics.
Look for "No config found for repo" or a closely worded equivalent.
Open Products → <your product> and confirm the repo is listed.

If both are true, this is the backend gap.

What to tell the operator

If you're reporting the issue, include:

The pipeline UUID (or the first eight characters from the URL).
The repo identifier shown in the error.
The product slug.
The time the pipeline was dispatched.

The operator-side resolution is a backend deploy. Nothing you can do in the UI changes it.

Permissions

Action	Who can do it
Read the failure	Any role.
Re-create the repo entry	Admin or owner.
Apply the backend fix	Operator side, not in the app.

Pipeline troubleshooting (overview) - symptom-based jump table.
Pipeline failed - generic Failed-state recovery.
Pipeline states - every state and badge color.

No config found for repo

On this page