Hi, I have the question regarding pre-verified contracts. I have the following situation: • My provider with version

P1

was verified with

C1

and the verification was successful. Provider with

P1

version was deployed to

prod

. • Then a new contract with

C2

version was published on a consumer’s side. But the

C2

contract is identical to

C1

contract, no discrepancies there. • I would expect that contract between

C2

and

P1

would be pre-verified automatically, since no changes in the contract were done. However, in my case this verification is missing (please see a screenshot of my matrix). Do you have any ideas why contract between

C2

and

P1

wasn’t pre-verified?

If it’s not pre-verified, it could be because of dynamic variables changing the hash of the contract

if there is no diff then the response body should be empty?

hmmm it seems to think something has changed, but it certainly doesn’t look that way!

and run a local

diff

Can it be done with HAL browser?

A diff between two pacts can, yes. But to rule out funkiness in the broker, I was suggesting it might be worth trying locally (on the two features/branches/commits) to see if it did indeed produce a different hash

ok, got it. Thank you for your support and ideas! 👍