- Cages Error Codes
Cages Error Codes
Quickly resolve Cages errors.
If you received a failed response from the Cage Run API that included an
X-Evervault-Error-Code header or if you received a JSON response with an
evervaultErrorCode field in the case of programmatic access, you can use this error code reference to help resolve the issue.
This error indicates that the cage run timed out as it took too long to complete.
Ensure all paths in your cage complete within the timeout specified in the Cages reference.
This error indicates that there was an issue decrypting the data passed to the cage.
Ensure that the data being passed to the cage was encrypted by the same team that owns the cage.
This error indicates that you are not authorized to access the resource you are requesting.
Ensure that you have included the correct api key in your request.
This error indicates that the server is unable (or refuses) to process the request sent by the client, due to an issue that is perceived by the server to be a client problem.
bad-request error is quite a vague error that doesn't indicate the exact issue but it is usually a client-side problem. Start by double checking that your cage name and version are correct.
If the issue persists, please contact support.
This indicates that the API is unable to find the resource you have requested.
The first step here would be to confirm that your cage name is correct. If that doesn't resolve your issue, please contact support.
This error indicates that there was an issue with Cages itself.
Try again in a few moments. If the issue persists, reach out to support.
This error indicates that the IP address of the client which invoked the Cage is not present in the IP whitelist.
Ensure that your Cage’s IP whitelist is correctly defined and includes any tenants that you expect to invoke the Cage.