We've had Slack notifications configured for some time without issues in all of our repos.
However, we've noticed recently that sometimes they work, and sometimes they don't.
In some cases, an engineers first pull request won't notify, but their second will, and we've seen this in reverse will the first PR will notify, but the second won't. It doesn't seem to have an affect on approvals, or merging, however.
We've tried removing the configuration from the repo and replacing, reauthorizing, clearing cache, etc, but to no avail.
Has anyone else experienced anything like this before?
Any additional steps I might be able to take to isolate further?
Hi Brett,
Last week we received one report about a similar issue via a support ticket and we are currently investigating this. I don't know if the issue you see is related to what the other customer reported, we would need to check logs. You can create a ticket with the support team for further investigation.
You can create a ticket via https://support.atlassian.com/contact/#/, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product. When you are asked to provide the workspace URL, please make sure you enter the URL of the workspace that is on a paid billing plan to proceed with ticket creation.
Kind regards,
Theodora
Thank you, Theodora, for taking the time to reply. Very much appreciated. I've followed your guidance above.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.