Violations Incorrectly Resolved Due to accidentally "Repo Deleted" event

We reproduced the status of the violations that were affected

We are currently testing our solution in our staging environment.

We identified the root cause as a race condition between the deployment of 2 micro services.
The impacted violations are from repositories that had branch deletions between June 16, 2025 at 8:36:35 PM GMT+3 to June 17, 2025 at 10:35:33 AM GMT+3
We’re still working on reopening the relevant violations.

We implemented a fix so further violations won’t be affected.
Working on re-opening the violations that were wrongfully resolved due to the issue. We will share an estimate when we can.

Description:
We’re currently investigating an issue where some violations are being incorrectly marked as resolved with the reason “Source removed” or “Repository deleted,” even though the associated repositories still exist and are active.

This issue has been reported by multiple users who have provided examples of violations incorrectly resolved due to a “deleted repository” when the repositories are, in fact, still present.

Impact:

Violations that should be open are marked as resolved.
Your actual code repositories remain untouched and functional; the issue is with how our system is processing and displaying the violation status.

Next Steps:
Our engineering team is treating this as a critical incident and is actively working to identify the root cause of these erroneous resolutions. We are gathering more data to accelerate our investigation. We’ll provide updates as soon as we have more information or a resolution.

We understand the urgency and impact of this issue and apologize for any disruption or confusion it may cause.