HTTP Error 429 - Too Many Requests to Pactflow

Hi, I’m occasionally seeing provider verification tests fail due to HTTP 429 Too Many Request errors connecting to Pactflow. It doesn’t happen often, but is a problem being reported to me by teams. We’re looking to continue to expand out contract testing (include more services/repos, more test coverage and implementation of the webhook), so this will only get worse.

I haven’t been able to find any documentation on what the limits are. I also can’t recreate the issue locally using a script that sends requests to pactflow. 200 requests using 10 threads and the same token completes just fine in less than a minute, all 200 responses. We shouldn’t be going anywhere near that (unless pactnet is doing something silly).

Some info about our usage:

  • Pactflow Enterprise cloud subscription
  • Contract tests run in CI/CD pipelines. Mostly using GitHub hosted runners, but sometimes a self-hosted runner inside our corporate network.
  • Multiple repositories/services (about 12 right now) are part of the same Pactflow team and share the same service account tokens (one read only, one read write).
  • Multiple pipelines from any single repository can run at the same time and thus run contract tests, connecting to pactflow, at the same time.
  • We’re using PactNet 5.0.1 (latest version at the time of this post).
  • Provider verification tests are pulling consumer contracts for multiple consumers/services as well as multiple versions of each (for latest of main branch as well as different versions deployed to different environments).

Example output from our pipeline. In this situation, all 15 provider verification tests failed.

Verifier Output

Failures:

  1. Failed to load pact - No pacts found for provider ‘[provider-name]’ matching the given consumer version selectors in pact broker ‘https://[customer_name].pactflow.io/’: IO Error - Request to pact broker path ‘’ failed: 429 Too Many Requests. URL: ‘https://[customer_name].pactflow.io/’

There were 1 pact failures
[xUnit.net 00:00:43.47] My.Product.ContractTests.VerifySomething [FAIL]

Verifier Logs

2026-11-17T12:21:53.629330Z INFO ThreadId(01) pact_verifier::pact_broker: Fetching path ‘’ from pact broker
2026-11-17T12:21:53.629347Z DEBUG ThreadId(01) pact_verifier::pact_broker: Final broker URL: https://[customer_name].pactflow.io/
2026-11-17T12:21:53.629389Z DEBUG ThreadId(01) reqwest::connect: starting new connection: https://[customer_name].pactflow.io/
2026-11-17T12:21:53.631981Z DEBUG ThreadId(01) hyper_util::client::legacy::connect::http: connecting to 13.227.87.47:443
2026-11-17T12:21:53.634085Z DEBUG ThreadId(01) hyper_util::client::legacy::connect::http: connected to 13.227.87.47:443
2026-11-17T12:21:53.842139Z ERROR ThreadId(01) pact_verifier: No pacts found for provider ‘[provider-name]’ matching the given consumer version selectors in pact broker ‘https://[customer_name].pactflow.io/’: IO Error - Request to pact broker path ‘’ failed: 429 Too Many Requests. URL: ‘https://[customer_name].pactflow.io/’
2026-11-17T12:21:53.842176Z ERROR ThreadId(01) pact_verifier: Failed to load pact - \x1b[31mNo pacts found for provider ‘[provider-name]’ matching the given consumer version selectors in pact broker ‘https://[customer_name].pactflow.io/’: IO Error - Request to pact broker path ‘’ failed: 429 Too Many Requests. URL: ‘https://[customer_name].pactflow.io/’\x1b[0m
2026-11-17T12:21:53.843775Z DEBUG ThreadId(01) pact_matching::metrics: Sending event to GA - {“cd3”: “linux-x86_64”, “cid”: “b6537da015622bae1a9ee55004422137”, “cd2”: “CI”, “cd6”: “pact_ffi”, “ec”: “ProviderTest”, “v”: “1”, “tid”: "[tid], “an”: “pact-net”, “t”: “event”, “aid”: “pact-net”, “aip”: “true”, “cd7”: “1.2.10”, “el”: “Pacts verified”, “ea”: “Completed”, “av”: “5.0.1.0”, “ds”: “client”, “ev”: “0”}
2026-11-17T12:21:53.850309Z DEBUG ThreadId(01) reqwest::connect: starting new connection: https://www.google-analytics.com/
2026-11-17T12:21:53.851799Z DEBUG ThreadId(01) hyper_util::client::legacy::connect::http: connecting to 142.251.211.14:443
2026-11-17T12:21:53.853758Z DEBUG ThreadId(01) hyper_util::client::legacy::connect::http: connected to 142.251.211.14:443
2026-11-17T12:21:53.879367Z DEBUG ThreadId(01) hyper_util::client::legacy::pool: pooling idle connection for (“https”, www.google-analytics.com)
2026-11-17T12:21:53.879424Z DEBUG ThreadId(01) pact_plugin_driver::plugin_manager: Shutting down all plugins

Failed My.Product.ContractTests.VerifySomething [384 ms]
Error Message:
 PactNet.Exceptions.PactVerificationFailedException : Pact verification failed
Stack Trace:
 at PactNet.Verifier.InteropVerifierProvider.Execute()
 at PactNet.Verifier.PactVerifierSource.Verify()
 [Redacted-stack-trace]
 at System.RuntimeMethodHandle.InvokeMethod(ObjectHandleOnStack target, Void** arguments, ObjectHandleOnStack sig, BOOL isConstructor, ObjectHandleOnStack result)
 at System.RuntimeMethodHandle.InvokeMethod(ObjectHandleOnStack target, Void** arguments, ObjectHandleOnStack sig, BOOL isConstructor, ObjectHandleOnStack result)
 at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args)
 at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
Standard Output Messages:

Starting verification…
Pact verification failed

Can anyone shed some light as to what the rate limit rules are and what can be done to avoid this? PactNet doesn’t have retry logic built into it.

Thanks,
Greg

Hey Greg,

I think this may be resolved in the next release of pact-net which will bump the underlying pact-ffi

I believe the verifier calls were made more tolerant in this PR

It was released in libpact v0.5.5 and pact-net 5.0.1 is still on 0.4.27

This PR in pact-net will bring it in

In the interim, the couple of workarounds are

  1. Use the verifier cli rather than pact-net itself, which includes the change, as well as a configurableoption
  2. Build the pact-net package with the above PR, and use that in your build.

Option 1 is an official route but requires changes to your verifier tests, Option 2 is unofficial but will mean there are no test changes, just building and installing from a local package (via the ditsribution medium of your choice)

Happy to help provide some guidance, as I have been working on the next batch of pact-net PR’s for more messaging and new plugin features.

Worth checking with Pactflow support whether the limit is per token, per account or per IP — sharing the same read-only/read-write tokens across 12 repos with concurrent pipelines may hit a per-token threshold your local 200-request script won’t reproduce. While waiting for the pact-net upgrade, try reducing burst concurrency (stagger pipelines or cap parallel verification jobs) and log the raw HTTP status and Retry-After header so 429s aren’t misreported as “No pacts found”. The ffi retry logic in 0.5.5 helps, but it’s mitigation rather than a fix for the underlying burst.