Hi all .. Thank you very much in advance for the help. We are having the following situation: Consumers are correctly publishing contracts to pactflow, since the content of the contract has not changed we expect the contract to be marked as verified by the provider which is already deployed to a given environment. But, this is not the case, the contract shows as not verified at all. Any ideas?

One common cause is the use of matchers/generators in your code that generate new values for the example (this seems to be common in the Java DSL where you can leave out an example and it generates a random value)

Thanks a lot, we will take a look to see if this is the case. Regards.

only if it generates a random value

That was actually the problem. Solved! Now, if we use this event trigger: Contract published that requires verification We don't understand why the verification is triggered if the content has not changed and the contract shows as verified. Thanks a lot!

@Julián Álvarez it will be triggered if the provider version in one of master/any deployed environment has changed

Thank you a lot!!!