Hi 🙂 I wanted to share with you what I'm seeing in my Pact Broker, and see if anyone can help me understand what's happening. We have set our Pact Broker image and our Webhook (reacting to the

contract_content_changed

event), and I was working on a consumer & provider sample repos. What is happening right now is that once the contract changes, the Webhook gets executed and makes a request to our internal CI tool, which runs the provider verification. Once that happens, the provider contract tests pass and the verification result is published. The issue I have is that, even the verification passed and the UI shows it

green

, we still see

red

on the Webhook status column (screenshot attached). If I go in to try to see what happened, I see that shows two webhook executions: one from a few days ago (that failed) and one from today (that succeeded). I have also attached an screenshot showing it. To me it looks like somehow it keeps showing an earlier webhook execution that failed, and I can't get "rid of it". Could you help me understand what's happening?

See if you can delete the failing triggered webhook through the HAL browser

How could I do that? The thing is that when I try to see the webhooks cerated in the Broker, I only see 1:

there’s 1 webhook, it’s been triggered multiple times for different events.

if you mean

...../webhooks/{webhookId}/triggered-webhooks

, I get a 404

yeah, sorry

should I remove the webhook and try to create it again?

it’s probably easiest 😆

but if you check the screenshoot in my main message, the event that triggered both was the same as far as I can see

in the HAL browser, on the webhook status resource, you should have a link of triggered webhooks in the resources section

What I don't understand is why I got that first execution (

triggeredWebhooks[0]

) that doesn't look like my created webhook... I guess I created a "bad" webhook at some point, and I'm paying the prize now 😅 😆

working out how to summarise all the webhook data into one status was tricky, and while I’m not convinced there’s a bug there, it might be showing data in an unexpected way.

Probably I messed something up while trying to create the webhook, I'm not sure there's a bug either. I was just trying to understand what could be going on, because I could mess it up again in a similar way in the future 😅

turn it off and on again 😆

it hasn't worked 😅 I tried to remove the webhook using a DELETE to

..../webhooks/{id}

, and it looked like it was deleted looking at the Broker UI. But then I created it again (2 times, the fist one I created it wrong and then I did it well), and it showed all the previous data, and all the previous executions are still there. Hence, I can't get a "green" status in the Broker UI because it still takes into account executions with deleted webhooks

oh, I wonder if there’s some logic in there that was too smart for this sitaution.

Only the last one has been executed with the existing version of the webhook

now I think about it, I think that the triggered webhooks are kept around when the webhook is deleted to ensure that a status can be calculated. sigh.

I guess so

you might need to clear the triggered webhooks table, if it’s important to you.

I was going to ask if there was any API endpoint to remove that data, or if I had to look at the DB directly

if you can’t identify the triggered webhook that’s failed, then you’ll need to go to the db.

DELETE to the triggered-webhook?

yes

let me try it

looks right

maybe the fact that those webhooks have been deleted matters here?

huh. ok, i never made a triggered webhook endpoint.

no worries, I'll try to do it and see it that does the trick 🙂

if it doesn’t, the only other way is to delete the whole database 💥

so, one final question. As far as I understand, once a webhook execution fails, we will have a "red" state in the broker UI until we have a newer one that succeeds. But if we at some point need to create a new version of the webhook, we will face this same issue if we had the previous version's last execution state as not-successful (either failed or retrying)

hm, you make a good point.

sounds good to me, but I don't know what side-effects that may have 😅 And yeah, I will create an issue there 🙂 Thank you very much for all the help!