Pact "No pacts found" for provider verification in CI

By Kaveh Alemi·Latchkey

Provider verification ran but found zero pacts to verify. Either the consumer never published a contract for this provider, the provider name does not match, or the broker version selectors excluded everything.

What this error means

Verification exits without running interactions, printing "No pacts found" or "0 interactions" for the provider, and the job passes or fails with nothing verified.

INFO: Fetching pacts for user-api from https://myorg.pactflow.io
WARN: No pacts found for provider 'user-api' matching the given selectors

Common causes

Provider name mismatch

The provider name in the verification config does not exactly match the name the consumer used when publishing, so the broker returns nothing.

Version selectors matched no pacts

Consumer version selectors (mainBranch, deployedOrReleased) exclude every published pact, or no consumer has published yet.

How to fix it

Match the exact provider name and selectors

1. Confirm the provider name equals what the consumer published against.
2. Use selectors that include existing pacts (for example the consumer main branch).
3. Verify in the broker UI that a pact for this pair exists.

verifier.setProviderInfo("user-api");
verifier.broker()
  .withSelectors(ConsumerVersionSelectors.mainBranch());

Publish a consumer pact first

If no consumer has published, run the consumer pact tests and publish before provider verification.

How to prevent it

• Keep provider names identical between consumer and provider config.
• Use selectors that include your active branches.
• Ensure the consumer publishes before provider verification runs.

Frequently asked questions

Related guides

References

• GitHub Actions documentation