Problem Statement

A projects' scan may get stuck or take an excessive amount of time while resolving dependencies, building the application or stitching call graphs.

A way to check is to use the API to see if the Projects' processing_status.scan_state is 'stuck' at SCAN_STATE_INGESTING. Use the following command to isolate these projects:

endorctl api list -r Project --filter 'processing_status.scan_state==SCAN_STATE_INGESTING'  --field-mask 'meta.name,processing_status.scan_state,processing_status.scan_time' --traverse

One of the most common messages (not all-inclusive) may be a CI-based or local scan occurring in parallel to an 'Agent-less' or App-based scan on Endor Labs' runners.

ERROR: There was an error initializing the repository details: A parallel automated scan is currently in process. Please wait ..

Note: Endor Labs' scheduler automatically check for Projects that have processing_status.scan_state==SCAN_STATE_INGESTING && processing_status.scan_time >= 48 hours. These projects that qualify are automatically reset back to SCAN_STATE_IDLE

Solution

A user can manually toggle the project back project state to SCAN_STATE_IDLE by running the following endorctl command:

endorctl api update -r Project --data '{"processing_status":{"scan_state": "SCAN_STATE_IDLE"}}' --field-mask "processing_status.scan_state" --uuid <UUID> --namespace <NAMESPACE>

Note: You must update the placeholder <uuid> and <namespace> template arguments from the example