Hey, What might cause a Pact to fail if all the interactions are successful?

are you seeing the same result on the matrix page?

@Candy Goodison yep appears to be consistent:

hmm not sure what could cause this, are you able to run 'can-i-deploy' locally? The console output might show a more informative error

So digging a bit deeper, the logs show this: There's some useful info in the (full) logs:

[Step 4/8]  Compiled provider version (optional): Some(1.0.0.771-855b70d)
[21:44:08][Step 4/8]  Starting verification...
[21:44:08][Step 4/8]  Pact verification failed
[21:44:08][Step 4/8]  
[21:44:08][Step 4/8]  Verifier Output
[21:44:08][Step 4/8]  ---------------
[21:44:08][Step 4/8]  The pact at <https://xero.pactflow.io/pacts/provider/ManualUpload.BFF/consumer/ManualUpload.SPA/pact-version/bf45cbec498cbe559fd77fccd3807d9273e99344> is being verified because the pact content belongs to the consumer version matching the following criterion:
[21:44:08][Step 4/8]      * consumer version(s) currently deployed to test (78047465772cce9c1e37edf0d09181761236670c)
[21:44:08][Step 4/8]  
[21:44:08][Step 4/8]  Verifying a pact between ManualUpload.SPA and ManualUpload.BFF

In particular:

The pact at [...] is being verified because the pact content belongs to the consumer version matching the following criterion: consumer version(s) currently deployed to test (78047465772cce9c1e37edf0d09181761236670c

We don't think that SHA (

78047465772cce9c1e37edf0d09181761236670c

) is deployed to any environment, definitely not

test

.

ah could be erroneous record deployment somewhere. Could try 'undeployment': https://docs.pactflow.io/docs/bi-directional-contract-testing/deploying/#recording-undeployments

I think we've figured this out.

test

was an old environment that we're no-longer supposed to be using. I think we will need to clear the record of that deployment, probably with https://docs.pact.io/pact_broker/recording_deployments_and_releases#recording-undeployments

Awesome, glad it's working now :)