Issue Summary

Sometimes slack notifications are not triggered for "build failed" repository-wide events.
 

Steps to Reproduce

1. Configure slack notifications for "build failed" as shown in the below screenshot, when you are using a third-party CI tool

2. When a build failed status is sent back to Bitbucket Cloud commit from the third-party CI tool via our API(or any plugin in the CI tool that uses our API)

Expected Results

It is expected that we receive a Slack notification for the build failure.

Actual Results

However, sometimes we might not receive a build failed notification.

This is because the slack webhook only has "repo:commit_status_updated" event and not "repo:commit_status_created"

Workaround

1. Use API to make a dummy update to the build status in the post-build actions of your build so that webhook will be triggered and a slack notification is sent.