You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for this. It looks like you also had this option set on the account (I can see a lot of the webhooks that were triggered were actually caused by this setting, and not the other).
I believe there may be an issue with the webhook button in pactflow triggering multiple executions that I can recreate, but I get the expected behaviour triggering the webhook directly via API
🤖 Great news! We've labeled this issue as smartbear-supported and created a tracking ticket in PactFlow's Jira (PACT-2563). We'll keep work public and post updates here. Meanwhile, feel free to check out our docs. Thanks for your patience!
Pre issue-raising checklist
I have already (please mark the applicable with an
x
):Software versions
Expected behaviour
I have this webhook page:
When I select a specific provider and click
Test Webhook
, I expect a webhook call from all possible consumer/provider pairs with this provider.Example:
I have 30 consumers and 10 providers.
Provider A has 3 consumers. Then I would expect 3 webhooks to be send out.
Actual behaviour
It seems that every possible consumer/provider constellation is send out spamming the endpoint receiving the webhook call.
Steps to reproduce
Test Webhook
You should just get 1 call as the chosen provider has only one consumer. But there will be 2.
Additional information
This issue was initially discussed in the pact slack workspace on the 3rd September 2024.
The conversation can be found here
In there it was pointed out that the logic would be somewhere in the trigger_service.rb.
The text was updated successfully, but these errors were encountered: