Service degradation affecting the Polaris SCA Scan Service associated with the Component Locator

Final update

We are pleased to confirm that the previously reported issue affecting Polaris SCA has been fully resolved, and normal service has been restored as of 6 pm EDT. All systems are now operating as expected. Our teams will continue to monitor closely to ensure ongoing stability. We appreciate your patience and understanding throughout this incident. Should you experience any further issues, please contact our support team.

1. Resolved · Sep 1, 22:16 UTC
   We are pleased to confirm that the previously reported issue affecting Polaris SCA has been fully resolved, and normal service has been restored as of 6 pm EDT. All systems are now operating as expected. Our teams will continue to monitor closely to ensure ongoing stability. We appreciate your patience and understanding throughout this incident. Should you experience any further issues, please contact our support team.
2. Identified · Aug 28, 17:17 UTC
   We are currently investigating a service degradation affecting the SCA Scan Service associated with the Component Locator. Our engineering team is actively investigating and working to restore normal operation as soon as possible. We will continue to provide periodic updates supplemented with additional updates as more information becomes available. We appreciate your patience while we work to resolve this issue. Scans Affected Polaris SCA scans On-prem and hosted bridge CLI-initiated SCA scans Manifestation Affected customers will experience scan failures with the following messages logged: Running Component Locator v2.4.2 Detect run failed. Index 1 out of bounds for length 1 Generating Component Location Analysis File for All Components: FAILURE Overall Status: FAILURE_UNKNOWN_ERROR Workaround Polaris Source Upload Scans: None Polaris SCM Scans: None Polaris, on-prem, or hosted bridge CLI Scans: Disabling Component Location Analysis (CLA) by modifying the bridge CLI command will allow scans to complete: ./bridge-cli.exe --stage polaris --input input.json --diagnostics detect.args='--detect.component.location.analysis.enabled=false' Limitations introduced by disabling CLA are outlined in the following Community article: Impact of Disabling Component Location Analysis (CLA) in Polaris SCA https://community.blackduck.com/s/article/Impact-of-Disabling-Component-Location-Analysis-CLA-in-Polaris-SCA Current Status A fix has been developed, has completed QA and end-to-end testing,
3. Identified · Aug 25, 05:49 UTC
   We are currently investigating a service degradation affecting the SCA Scan Service associated with the Component Locator. Our engineering team is actively investigating and working to restore normal operation as soon as possible. We will continue to provide periodic updates supplemented with additional updates as more information becomes available. We appreciate your patience while we work to resolve this issue. Scans Affected Polaris SCA scans On-prem and hosted bridge CLI-initiated SCA scans Manifestation Affected customers will experience scan failures with the following messages logged: Running Component Locator v2.4.2 Detect run failed. Index 1 out of bounds for length 1 Generating Component Location Analysis File for All Components: FAILURE Overall Status: FAILURE_UNKNOWN_ERROR Workaround Polaris Source Upload Scans: None Polaris SCM Scans: None Polaris, on-prem, or hosted bridge CLI Scans: Disabling Component Location Analysis (CLA) by modifying the bridge CLI command will allow scans to complete: ./bridge-cli.exe --stage polaris --input input.json --diagnostics detect.args='--detect.component.location.analysis.enabled=false' Limitations introduced by disabling CLA are outlined in the following Community article: Impact of Disabling Component Location Analysis (CLA) in Polaris SCA https://community.blackduck.com/s/article/Impact-of-Disabling-Component-Location-Analysis-CLA-in-Polaris-SCA Current Status The root cause of the issue has been identified, a fix has been de
4. Identified · Aug 25, 05:47 UTC
   We are currently investigating a service degradation affecting the SCA Scan Service associated with the Component Locator. Our engineering team is actively investigating and working to restore normal operation as soon as possible. We will continue to provide periodic updates supplemented with additional updates as more information becomes available. We appreciate your patience while we work to resolve this issue. Scans Affected Polaris SCA scans On-prem and hosted bridge CLI-initiated SCA scans Manifestation Affected customers will experience scan failures with the following messages logged: Running Component Locator v2.4.2 Detect run failed. Index 1 out of bounds for length 1 Generating Component Location Analysis File for All Components: FAILURE Overall Status: FAILURE_UNKNOWN_ERROR Workaround Polaris Source Upload Scans: None Polaris SCM Scans: None Polaris, on-prem, or hosted bridge CLI Scans: Disabling Component Location Analysis (CLA) by modifying the bridge CLI command will allow scans to complete: ./bridge-cli.exe --stage polaris --input input.json --diagnostics detect.args='--detect.component.location.analysis.enabled=false' Limitations introduced by disabling CLA are outlined in the following Community article: Impact of Disabling Component Location Analysis (CLA) in Polaris SCA https://community.blackduck.com/s/article/Impact-of-Disabling-Component-Location-Analysis-CLA-in-Polaris-SCA Current Status The root cause of the issue has been identified, a fix has been de
5. Identified · Aug 21, 22:39 UTC
   We are currently investigating a service degradation affecting the SCA Scan Service associated with the Component Locator. Our engineering team is actively investigating and working to restore normal operation as soon as possible. We will continue to provide periodic updates supplemented with additional updates as more information becomes available. We appreciate your patience while we work to resolve this issue. Scans Affected Polaris SCA scans On-prem and hosted bridge CLI-initiated SCA scans Manifestation Affected customers will experience scan failures with the following messages logged: Running Component Locator v2.4.2 Detect run failed. Index 1 out of bounds for length 1 Generating Component Location Analysis File for All Components: FAILURE Overall Status: FAILURE_UNKNOWN_ERROR Workaround Polaris Source Upload Scans: None Polaris SCM Scans: None Polaris, on-prem, or hosted bridge CLI Scans: Disabling Component Location Analysis (CLA) by modifying the bridge CLI command will allow scans to complete: ./bridge-cli.exe --stage polaris --input input.json --diagnostics detect.args='--detect.component.location.analysis.enabled=false' Limitations introduced by disabling CLA are outlined in the following Community article: Impact of Disabling Component Location Analysis (CLA) in Polaris SCA https://community.blackduck.com/s/article/Impact-of-Disabling-Component-Location-Analysis-CLA-in-Polaris-SCA Current Status The root cause of the issue has been identified and a fix is in pr
6. Identified · Aug 21, 18:01 UTC
   We are currently investigating a service degradation affecting the SCA Scan Service associated with the Component Locator. Our engineering team is actively investigating and working to restore normal operation as soon as possible. We will continue to provide periodic updates supplemented with additional updates as more information becomes available. We appreciate your patience while we work to resolve this issue. Scans Affected Polaris SCA scans On-prem and hosted bridge CLI-initiated SCA scans Manifestation Affected customers will experience scan failures with the following messages logged: Running Component Locator v2.4.2 Detect run failed. Index 1 out of bounds for length 1 Generating Component Location Analysis File for All Components: FAILURE Overall Status: FAILURE_UNKNOWN_ERROR Workaround Polaris Source Upload Scans: None Polaris SCM Scans: None Polaris, on-prem, or hosted bridge CLI Scans: Disabling Component Location Analysis (CLA) by modifying the bridge CLI command will allow scans to complete: ./bridge-cli.exe --stage polaris --input input.json --diagnostics detect.args='--detect.component.location.analysis.enabled=false' Limitations introduced by disabling CLA are outlined in the following Community article: Impact of Disabling Component Location Analysis (CLA) in Polaris SCA https://community.blackduck.com/s/article/Impact-of-Disabling-Component-Location-Analysis-CLA-in-Polaris-SCA Current Status The root cause of the issue has been ident