--- sourceDocument: Brazil Impact sourceDocumentLink: https://www.servicenow.com/docs/r/impact Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Impact ft:clusterId : - ipact bundleId : - ipact --- # Scan Engine API error codes # Scan Engine API error codes {#ariaid-title1} Release version: Brazil Updated November 5, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Error codes returned by the Scan Engine API, organized by HTTP status code. Each section includes proposed solutions and handling strategies. ## 400 Bad Request errors {#api-error-codes-grouped__section_400_errors} Validation errors indicate a problem with your request. Review the error message and correct the field or value before retrying. {#api-error-codes-grouped__table_400_errors__entry__3} | Error Code | Applies to endpoints | Description | |-|-|-| | DEFINITION_NOT_FOUND | GET /findings | The scan definition specified in your query does not exist. Verify the definition sys_id or number. | | INVALID_APPLICATION | POST /scan (application_scan mode) | The supplied application sys_id does not exist or is invalid. Verify the sys_id matches a valid application record. | | INVALID_FIELD_VALUE | POST /scan, POST /cancel, GET /findings, GET /resolved_findings | A field value does not match the expected format or type. Check the error detail for which field needs correction. | | INVALID_SCAN_MODE | POST /scan | The `scan_mode` value is not recognized. Verify it matches one of the supported modes: `instance_scan`, `update_set`, `application_scan`, or `content`. | | INVALID_UPDATE_SET | POST /scan (update_set mode) | The supplied update set sys_id does not exist or is invalid. Verify the sys_id matches a valid application record. | | INVALID_XML_CONTENT | POST /scan (content mode) | The XML content is not well-formed or is missing the `` root element. Validate the XML structure. | | MISSING_REQUIRED_FIELD | All endpoints | A required field is missing from your request. Check the error message to identify which field is required. | [Table 1. 400 Bad Request error codes] {#api-error-codes-grouped__table_400_errors} ## 401 Unauthorized errors {#api-error-codes-grouped__section_401_errors} Authentication errors occur when credentials are invalid. Refresh your credentials and retry immediately. Log the error for audit purposes. {#api-error-codes-grouped__table_401_errors__entry__3} | Error Code | Applies to endpoints | Description | |-|-|-| | NOT_AUTHENTICATED | All endpoints | Your session token or OAuth credentials are invalid, expired, or missing. Re-authenticate and retry with valid credentials. | [Table 2. 401 Unauthorized error codes] {#api-error-codes-grouped__table_401_errors} ## 403 Forbidden errors {#api-error-codes-grouped__api-error-codes-grouped} Authorization errors are configuration issues. Contact your administrator to grant the required role. don't retry automatically. {#api-error-codes-grouped__table_403_errors__entry__3} | Error Code | Applies to endpoints | Description | |-|-|-| | NOT_AUTHORIZED | All endpoints | Your user account does not have the `sn_se.scan_engine_user` role. Contact your administrator to request access. | [Table 3. 403 Forbidden error codes] {#api-error-codes-grouped__table_403_errors} ## 404 Not Found errors {#api-error-codes-grouped__section_404_errors} Resource not found errors occur when the requested scan or resource does not exist. Verify identifiers are correct and the resource has not been purged. {#api-error-codes-grouped__table_404_errors__entry__3} | Error Code | Applies to endpoints | Description | |-|-|-| | APPLICATION_SCAN_NOT_FOUND | GET /findings | No findings exist for the specified application scan. The scan may not have completed or the application ID may be incorrect. | | INSTANCE_SCAN_NOT_FOUND | GET /findings | No findings exist for the specified instance scan. The scan may not have completed or the scan result may have been purged. | | NO_ACTIVE_SCAN | POST /cancel | No active scan is running and no identifier was provided. Supply either `scan_sys_id` or `scan_number`, or verify a scan is currently active. | | SCAN_NOT_FOUND | GET /scan_status, GET /findings, GET /resolved_findings, POST /cancel | The scan result ID provided does not exist or has been purged. Verify the scan_result_sys_id or scan_number is correct. | | UPDATE_SET_SCAN_NOT_FOUND | GET /findings | No findings exist for the specified update set scan. The scan may not have completed or the update set ID may be incorrect. | [Table 4. 404 Not Found error codes] {#api-error-codes-grouped__table_404_errors} ## 409 Conflict errors {#api-error-codes-grouped__section_409_errors} Conflict errors occur when a request can't be completed due to the current state. For rate limiting (CONCURRENT_SCAN_RUNNING), implement exponential backoff starting with a 30-second wait, then increase on subsequent retries. {#api-error-codes-grouped__table_409_errors__entry__3} | Error Code | Applies to endpoints | Description | |-|-|-| | ALREADY_CANCELLED | POST /cancel | The scan is already in a Cancelled state. No further cancellation is needed or possible. | | CONCURRENT_SCAN_RUNNING | POST /scan | Another scan is already running for this target. Wait at least 30 seconds and retry, or cancel the existing scan first. | | SCAN_COMPLETE | POST /cancel | The scan has already completed and cannot be cancelled. Cancellation is only available for in-progress or queued scans. | [Table 5. 409 Conflict error codes] {#api-error-codes-grouped__table_409_errors} ## 413 Payload Too Large errors {#api-error-codes-grouped__section_413_errors} Payload size errors occur when the request body exceeds limits. Reduce the request size by using smaller batches or fewer records. {#api-error-codes-grouped__table_413_errors__entry__3} | Error Code | Applies to endpoints | Description | |-|-|-| | PAYLOAD_TOO_LARGE | POST /scan, POST /cancel | Request body exceeds 64KB. Reduce the request size by using smaller batches or fewer records. | [Table 6. 413 Payload Too Large error codes] {#api-error-codes-grouped__table_413_errors}