Hi! I got another doubt .. we have a service which is provider and consumer ... when we request can-i-deploy through the api: https://pactflow.xxx.io/can-i-deploy?pacticipant=yyyyyy&version=zzzzzzz&environment=dev The response is true ... all good, we are happy ... but when we do the verification with pact-broker command line tool from Jenkins it says no ...

pact-broker can-i-deploy --pacticipant=yyyyy--broker-base-url=<https://pactflow.xxxx.io> --broker-token=**** --version=zzzzzzzz --to-envionrment=dev

CONSUMER              | C.VERSION  | PROVIDER              | P.VERSION  | SUCCESS? | RESULT#
----------------------|------------|-----------------------|------------|----------|--------
wwwwwwwwwwwwwwwwwwww  | e22e444... | yyyyyyyyyyyyyyyyyyyyy | b5b0a6c... | true     | 1      
yyyyyyyy              | b5b0a6c... | kkkkkkkkkkkkkkk       | ???        | ???      |

Any ideas what could we be missing? Thanks a lot in advance, much appreciated the help. Regards!

hi @Julián Álvarez there’s nothing obviously wrong in what you’re doing. You should have the same results. I can’t identify the problem based on the information you’ve given. You can raise an issue by sending an email to support@pactflow.io. Please include the full HTTP logs of both scenarios. You can turn on the HTTP logs for the can-i-deploy command by adding

--verbose

. If you are using the onprem product, then you’ll need to also include the server side logs for each of those requests - you’ll be able to identify them using the X-Request-Id response header that you’ll see in the HTTP logs.