Pact Broker "404 ... no pact found" in CI

The broker resolved the request but has no pact resource matching the consumer/provider pair or the specific version requested. 404 here is "nothing published", not an auth or network fault.

What this error means

A verify or fetch step fails with "404 Not Found" for a broker pact URL, or the verifier reports "no pact found" for the consumer/provider combination.

Pact

GET https://acme.pactflow.io/pacts/provider/orders-provider/consumer/web-consumer/latest
404 Not Found
{"error":"No pact found for consumer web-consumer and provider orders-provider"}

Common causes

The consumer never published a pact for this pair

No consumer build published a contract against this provider, so there is nothing at that URL.

The consumer or provider name is misspelled

A name mismatch between publish and verify points the request at a resource that does not exist.

How to fix it

Publish the consumer pact first

Run the consumer contract tests to generate the pact.
Publish it to the broker with a real version.
Re-run provider verification once the pact exists.

Terminal

pact-broker publish ./pacts \
  --consumer-app-version "$GIT_SHA" \
  --branch "$GIT_BRANCH" \
  --broker-base-url "$PACT_BROKER_BASE_URL"

Reconcile the consumer/provider names

Ensure the names used at publish exactly match those used at verify; even case differences produce a 404.

How to prevent it

Publish consumer pacts before running provider verification.
Keep consumer and provider names identical across all jobs.
Check the broker UI to confirm the pact exists before debugging deeper.