Stuck SAST Scans

We’ve identified the root cause of the incident as a bad code change combined with lag in the offline topic of the scan service. We are currently reverting the code change.

The lag has cleared, so the impact is now limited. Customers can trigger a new scan either through the UI (Rescan) or by commenting #cycode_sast_rescan on the PR.

We will continue to monitor the system as it stabilizes.

Description:
We’re currently experiencing an issue with SAST scanning on pull requests.

Current Status:
Our team is investigating the root cause and working to restore full scanning functionality.

Impact:
Pull requests SAST Scans may not display accurate SAST results until the issue is resolved.

Next Update:
We will provide an update as soon as we have more information.