In the User's Interface, we can verify the status of scans via the "Jobs" menu.
It appears that on some specific occasions, when a scan runs immediately after another one has been completed, the new one will remain "Pending" for a while and be marked as "aborted".
In this example, we can see that 1 scan completed successfully at 17:08:29, but less than 1minute and 30 seconds after, another scan was run and was aborted :
The explanation to this is because we have an internal mechanism which is checking if the job which was used to complete the previous scan, has been removed from the GCloud Pod.
Until this job is removed, no other scan can be initiated.
This is necessary to preserve the system from running multiple scans at the same time.
In the meantime, the job doesn't immediately get removed after the scan completed. This is why we can face this behavior.
Additionally to this, we have a timeout mechanism which causes the system to self-abort the job after a certain amount of time spent in "pending" status.
This behavior will be improved in next releases, preventing from this side effect.
If this problem occurs, we have a workaround:
- Abort the scan remaining in "Pending" status
- Wait for 15 minutes to make sure the previous job has been removed.
- Launch the scan again
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article