Hey there 👋 I’ve had some engineers reach out to me about their can-i-deploy failing It seems that their BDCT integration hasn’t verified the interactions between a consumer branch and the provider version that’s deployed in an environment - is there a way to force that verification to take place?

hmm that’s odd. If it didn’t kickoff on publish, it should kickoff when

can-i-deploy

runs

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

Sure thing thanks Matt!