Amazon Neptune
User Guide (API Version 2017-11-29)

Neptune Loader Error and Feed Messages

The following messages are returned by the status endpoint of the Neptune Loader. For more information, see Overall and Feed Status Descriptions.

The following table contains loader feed code and description.

Error or Feed Code Description

LOAD_NOT_STARTED

Load has been recorded but not started.

LOAD_IN_PROGRESS

Load has started and is in progress.

LOAD_COMPLETED

Load has completed without any errors or errors within an acceptable threshold.

LOAD_CANCELLED_BY_USER

Load has been cancelled by user.

LOAD_CANCELLED_DUE_TO_ERRORS

Load has been cancelled by the system due to errors.

LOAD_UNEXPECTED_ERROR

Load failed with an unexpected error.

LOAD_FAILED

Load failed as a result of one or more errors.

LOAD_S3_READ_ERROR

Feed failed due to intermittent or transient Amazon S3 connectivity issues. If any of the feeds receive this error, overall load status is set to LOAD_FAILED.

LOAD_S3_ACCESS_DENIED_ERROR

Access was denied to the S3 bucket. If any of the feeds receive this error, overall load status is set to LOAD_FAILED.

LOAD_COMMITTED_W_WRITE_CONFLICTS

Loaded data committed with unresolved write conflicts.

The loader will try to resolve the write conflicts in separate transactions and update the feed status as the load progresses. If the final feed status is LOAD_COMMITTED_W_WRITE_CONFLICTS, then try resuming the load and it will likely succeed without write conflicts. A write conflict is not usually related to bad input data, but duplicates in data can increase the likelihood of write conflicts.

LOAD_DATA_DEADLOCK

Load was automatically rolled back due to deadlock.

LOAD_DATA_FAILED_DUE_TO_FEED_MODIFIED_OR_DELETED

Feed failed because file was deleted or updated after load start.