Pact Foundation

Screenshot 2024-02-15 at 22.18.06.png

however, I find myself in a position where this is precisely what’s happening. Have I missed anything?

If you look at the logs for them, you might see that each invocation is for a different version of the provider, that has not verified the contract (e.g. a new branch)

fair point, let me double check just in case

while we’re on the subject: are the provider versions in the event the provider versions that need to verify this contract?

because I find this example very confusing if so, check this out `variables[PACT_PROVIDER_VERSION]=d76b15dbab276a17d7ad3cbb69b64b21d27c1027` that’s in the webhook, however when I go check that commit I see
```Commit d76b15db  authored 1 year ago by Ulises Cervino's avatar Ulises Cervino```
which strikes me as odd?

Interesting.

&gt; Using this webhook event allows the changed pact to be tested against the head of the providers main branch and any deployed or released versions of the provider, in the same way as the consumer version selectors can be configured to allow the head of the consumers main branch and any deployed or released versions of the pact to be tested against a version of the provider.
I’m hoping that version corresponds to one of these conditions

If it doesn’t, I could get the team to investigate to find out what’s happening

Thanks. Hate to ask but I'll need a support ticket as it will require the beginner to have access to your data

Please create a ticket here with the issue details so that we can properly track the resolution and the PactFlow product support team will continue to work through it with you: <https://support.smartbear.com/pactflow/message>

how much detail do you need there? or is this a token ticket just to get going?

```The following unique identifier was assigned to your request: 00597219```


That’ll do, I’ll let the CC team know to forward it straight to L3 support - thanks!