Error Catalog
The error codes in the table below describe the codes that you may encounter while working with the Snyk API or CLI. When errors are encountered using the API, they will also have an appropriate HTTP status code. If you encounter errors without an error code, use the HTTP status code to determine the appropriate action.
Service temporarily throttled
The request rate limit has been exceeded. Wait a few minutes, then try again.
Server error response
The server doesn’t recognize the request method, or it cannot fulfill it. Review the request and try again.
Help Links:
Client request cannot be processed
The server cannot process the request due to a client error, such as malformed request syntax, size too large, invalid request message framing, or deceptive request routing. Review the request and try again.
Server communication error
The server timed out during the request. Check Snyk status, then try again.
Help Links:
Authentication error
Authentication credentials not recognized, or user access is not provisioned. Revise credentials and try again, or request access from your Snyk administrator.
Request not fulfilled due to server error
The server cannot process the request due to an unexpected error. Check Snyk status, then try again.
Help Links:
Bad request
The server cannot process the request due to invalid or corrupt data. Review the request, then try again.
Help Links:
Forbidden
Access to the requested resource is forbidden.
Not acceptable
The server cannot provide a response that matches the provided accept headers. Review the request, then try again.
Not found
The server cannot find the requested resource.
Method not allowed
The target endpoint does not support your request method. Review the request, then try again.
Request entity too large
The request entity exceeds server limitations.
Unauthorized
The request lacks authentication credentials for the requested resource.
Help Links:
Unsupported media type
The media format of the request is not supported.
Unsupported Ecosystem
The language or package manager is not supported.
Help Links:
Unable to parse manifest file
The provided manifest file could not be parsed as it has invalid syntax or does not match the expected schema. Review the manifest file, then try again.
Lock file out of sync with manifest file
Some of the dependencies that are expected to be in the lock file are missing, usually indicating that the lock file is out of sync with the provided manifest file. Re-sync the lock file, then try again.
Unable to parse lock file
The provided lock file could not be parsed as it has invalid syntax or does not match the expected schema. Review the lock file, then try again.
Unknown dependency version
Dependency version could not be resolved.
Help Links:
Payload missing required elements
The server could not process the request.
Files cannot be processed
The dependency service could not process the files.
Source is not supported
The source used is not supported by fetcher. The supported sources are: github, bitbucket, gitlab.
Cannot get file from source
Could not get the file from the source URL.
No released version for versions range
There was no version released for the specified versions range.
Timeout when processing the dependency tree
There was an timeout when processing the dependecy tree.
Received more manifests than expected
Too many manifest files were provided in the request body.
Failed to apply dependency updates
An error occured while updating dependencies.
Unknown blob encoding on Github
Unknown blob encoding on Github.
No result from forked process
No result from forked process.
Child Process Execution Error
The child process encountered an error during execution.
No valid package upgrades
The system attempted to find valid upgrades for the packages specified in the lock file, but none were available.
No dependency updates
There are no available updates for the dependencies.
Missing required request header
The server encountered a request that is missing a mandatory request header.
Could not parse JSON file
An error occurred while attempting to parse a JSON file.
Could not Base64 encode
An error occurred while attempting to perform Base64 encoding.
Could not Base64 decode
An error occurred while attempting to perform Base64 decoding.
Missing supported file
Could not find supported file.
Missing environment variable
The server encountered a critical operation that requires a specific environment variable, but the variable is not set or is not accessible within the current environment.
No output from isolated builds
The response from isolated builds had no output.
Failed to relock
An error occurred while attempting to relock.
Invalid configuration
The configuration parameter does not meet the expected data type. Please ensure the provided value is of the correct data type.
Unsupported manifest file type for remediation
The provided manifest file is not supported by Snyk for .NET.
Help Links:
Target framework not supported
The provided manifest file defines a
<TargetFramework> or <TargetFrameworks> that is not currently supported by Snyk's .NET scanning solution.Failed to access private module
Snyk could not access the private modules within your go.mod files.
Help Links:
Go mod file not found
A go.mod file was not found in the current directory or any parent directory.
Help Links:
OAuth re-authorization required
Your code is cloned on an isolated environment using Git as it is required by Snyk to analyze its dependencies.
Your Organization has enabled or enforced SAML SSO after you authorized Snyk to access your code, and a re-authentication is therefore required.
The error you're seeing is usually reproducible by attempting to do a
git clone of your repository with incorrectly configured credentials. Verify your authentication configuration with your Git cloud provider and try again.Help Links:
Your project repository is missing required files
Generating the dependency graph requires Snyk to run go list
go list -deps -json inside the Project. If the operation fails, creating a full dependency graph cannot continue.This error usually means that you need some cleanup, such as
go mod tidy) or your Project deployment process contains a code generation step such as protobuf or something similar that is not currently supported by Snyk.To verify if this is the case, clone your Project in a clean environment, run go list
go list -deps -json and verify whether the operation fails.If Snyk cannot process your code successfully, insert the Snyk CLI as part of your deployment pipeline.
Help Links:
Missing property
The required property is missing from the pom object.
Unable to resolve value for property
The targeted property could not be resolved with a valid value.
Unable to resolve version for property
The targeted property could not be resolved with a valid version.
Cyclic property detected in POM file
There is circular dependency among properties in the Maven project's configuration file (POM), preventing proper resolution and causing an error.
Error parsing the XML file
There is an error parsing the XML file. This could be referring to either pom.xml or maven-metadata.xml.
Invalid coordinates provided
The coordinates provided for a project were invalid.
Skipping group
Skipping a specific groupId starting due to remapped coordinates.
Pom file not found
The pom file was not found in Maven repository.
Missing project from POM
A project element is missing from POM.
Cannot resolve the target POM from the input XML
Cannot resolve the targeted POM from the input XML.
Cannot resolve the target POM from the repository
Cannot resolve the targeted POM from the repository.
Cannot get the build file repository
Cannot get the build file repository.
Unable to create hosted git info
Cannot create source URL.
No repository found for A NPM package
No repository found for the NPM package.
Could not parse NPM registry URL
Could not parse NPM registry URL.
Could not find a broker resolved URL
Could not find a broker resolved URL.
Unable to replace broker URL
Unable to replace all broker urls in lock file.
Bad NPM version
The NPM version is not supported.
Unsupported manifest file type for remediation
The provided requirements file is not supported by Snyk for Python.
Help Links:
Invalid request
The provided request payload is not valid for the selected ecosystem. Please review the API documentation.
Help Links:
Build environment not found
The build environment for the provided context could not be found. Please ensure you have created the build environment first.
SBOM generation export server error
An unexpected error occurred during the SBOM generation. Review the request, then try again. If the error persists, contact Snyk Support.
Dependency graph error
An unexpected dependency graph error occurred. Review the request, then try again. If the error persists, contact Snyk Support.
Error parsing dependency graph
The dependency graph cannot be parsed due to an unexpected error. Review the request, then try again. If the error persists, contact Snyk Support.
SBOM not supported due to project type
Only SBOMs for Snyk Open Source or Snyk Container projects are supported.
SBOM not supported
Only SBOMs for open source projects are supported (Snyk Open Source).
Dependency graph request cannot be processed
The server cannot process the request due to incomplete data. Review the request, then try again.
Authorization failed due to missing API token
The API token is misconfigured or expired. Configure or generate the API token, then try again.
Help Links:
Client request cannot be processed
The body of the request is empty. Review the request, then try again.
Invalid dependency graph
The request cannot be processed due to an internal error. Review the request, then try again.
Maven search service unavailable
The upstream Maven search service is not available.
Help Links:
SHA1 not found
Unable to find the coordinates for the provided SHA1.
Help Links:
Your Organisation is not authorized to perform this action
You likely don’t have access to the features in Beta. To get access, you can request access to features in Beta through your account manager or team.
Authorization request failure
Unexpected error when authenticating. Try again, and if the error still occurs, contact support.
Invalid purl
Make sure that the purl is valid. See the Package URL specification link for further information.
Help Links:
Namespace not specified
You have requested a package type that requires a namespace (e.g. maven group id). Provide the namespace to retrieve the package.
Help Links:
Unsupported ecosystem
The package type is not supported. Check the List issues for a package in Snyk API.
Purl components required
A list of components of the purl spec is required. The purl did not specify all the required components.
Unsupported purl components
Remove the unsupported component and retry the request.
Go version format not supported
Go pseudo version not supported.
Requested package not found
The package you specified in the purl cannot be found in the vulnerability database. Check the package name, ecosystem, and version, then try again.
Vulnerability service not available
This issue is unexpected, and the service will recover shortly. If the error still occurs, contact support.
This issue is unexpected and the service should recover quickly if not please contact support
An unexpected error occurred. Please try again, and if you continue to experience issues please contact support.
This issue is unexpected and the service should recover quickly if not please contact support
An unexpected error occurred with the vulnerability service. Please try again, and if you continue to experience issues please contact support.
Request not processed due to unexpected error
This issue is unexpected, and the service will recover shortly. If the error still occurs, contact support.
Invalid pagination parameters
The pagination limit is > 1 and ≤ 1000, and the offset is ≥0.
purls exceed limit
The number of purls sent in the request exceeds the limit of 1000 set by the service.
Number of issues exceeds limit
The number of issues found for the provided purls exceeds the limit defined by the API. Reduce the number of purls sent in a single request.
Expected distro to be present
The given Package URL does not have a required distro qualifier.
Help Links:
Unsupported Debian distro
This Debian distro is currently not supported.
Expected namespace to be present
The given Package URL does not have a required namespace.
Unsupported vendor
The given Package URL does not contain a supported vendor.
Invalid request
Check the body of your request and try again.
Unable to return valid API response
This issue is unexpected, and the service will recover shortly. If the error still occurs, contact support.
Failed to process data
This issue is unexpected, and the service will recover shortly. If the error still occurs, contact support.
Failed to store issue data
Check inputs and then try again. If the error still occurs, contact support.
Internal server error
This issue is unexpected, and the service will recover shortly. If the error still occurs, contact support.
Invalid request
Check the body of your request and try again.
Unable to return valid API response
This issue is unexpected, and the service will recover shortly. If the error still occurs, contact support.
Failed to process data
This issue is unexpected, and the service will recover shortly. If the error still occurs, contact support.
Failed to store snapshot data
Check inputs and then try again. If the error still occurs, contact support.
Internal server error
This issue is unexpected, and the service will recover shortly. If the error still occurs, contact support.
Failed to get pull request attributes
Snyk could not get the custom pull request template attributes, using the given variables and the fetched pr template.
Help Links: