Select Language:
If you’re working in a Code Review and trying to change the status of a finding to “False positive,” but encounter an error saying “The specified pentest job does not exist,” here’s what you can do to solve the issue.
First, confirm that you’re on the findings tab and selecting the correct finding. When you click on the finding and try to change its status, the system sends a POST request to an endpoint: https://securityagent.us-west-2.api.aws/UpdateFinding. You can verify this request in your browser’s network tab.
Next, look at the request payload, which should include details like findingId, agentSpaceId, status, and agentInstanceId. Even though these data points are correctly filled in, the system might still throw an error, especially if the response shows a 404 status with the message: “The specified pentest job does not exist.”
This error usually means that the system cannot find the related pentest job associated with the finding. The most common reason for this is that the pentest job has either been deleted or not properly linked to the current finding.
To resolve this problem, try the following steps:
- Double-check the finding’s details to confirm it’s linked to an active and existing pentest job.
- Verify that the pentest job exists in your system and hasn’t been removed or marked as completed.
- If the linked pentest job no longer exists, you may need to update the finding or contact your system administrator to re-establish the link.
- Sometimes, refreshing the page or logging out and back in can resolve temporary glitches.
If you still encounter issues after these steps, consider reaching out to your support team. Provide them with the request details and error message so they can diagnose if there’s a backend problem or a configuration issue.
By making sure the pentest job exists and is properly linked, you’ll be able to change the finding status without errors.
ChatGPT
Perplexity
Gemini AI
Grok AI
