Errors
Overview
This section is for developers and contains details about the various custom CheckAnything errors.
It includes information regarding reasons for the errors, error details, and other helpful information.
Notes
- Attributes are data elements (key, value pairs) in AWS events such as for Lambda functions and DynamoDB streams.
- Parameters are inputs to functions or methods.
- Data errors relate to database operations.
Details
Details for each custom CheckAnything error.
| Description |
A required attribute was not provided |
| Details |
Attributes are data elements (key, value pairs) in AWS events such as for Lambda functions and DynamoDB streams. |
| Description |
The value of an attribute that is immutable was provided that differs from the existing value. |
| Details |
Attributes are data elements (key, value pairs) in AWS events such as for Lambda functions and DynamoDB streams. |
| Description |
A change has been made by another process. This change can not be persisted. |
| Details |
The change being applied was not able to be made and has been aborted. |
| Description |
A configuration value is missing. |
| Details |
This may occur when a configuration value does not exist or exists but has no value.
Generally, the configuration value will be created if missing and set to a default value and this exception is thrown when the
NOT_ASSIGNED (constant) value is detected.
|
| Description |
An attempted data operation resulted in a database constraint violation. |
| Details |
The attempted database operation violated one or more constraints and the operation did not succeed.
|
| Description |
An attempt was made to delete data that was not permitted. |
| Details |
The attempted data deletion was not permitted and the operation did not succeed.
|
| Description |
There was an error accessing DynamoDB. |
| Details |
There was an error either accessing DynamoDB or with the DynamoDB command and the operation did not succeed.
|
| Description |
An attempted data operation would have resulted in duplicate data. |
| Details |
The attempted database operation violated a uniqueness constraint and the operation did not succeed.
There may be one or more uniquness constraints. All constraints will be returned without any guidance on which one(s) caused the constraint violation.
This is due to the error being thrown by DynamoDB which does not provide details on the specifics of the constraint violation.
|
| Description |
An attribute value is invalid, apart from being empty or null. |
| Details |
Attributes are data elements (key, value pairs) in AWS events such as for Lambda functions and DynamoDB streams.
|
| Description |
An data value is invalid, apart from being empty or null. |
| Details |
Data is considered invalid if it violates some application logic.
Invalid data errors are different than a database constraint violation.
Data validation typically takes places prior to data operations in order to provide more meaningful error messages.
|
| Description |
Lambda function invocation failure. |
| Details |
Lambda invocation has failed for some reason.
|
| Description |
A required parameter was not provided, including value being blank or null. |
| Details |
Parameters are inputs to functions or methods. |
| Description |
Data not returned from database query. |
| Details |
Expected data was not returned from database query when a result is expected. |