Neptune Loader Error and Feed Messages - Amazon Neptune
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Neptune Loader Error and Feed Messages

The following messages are returned by the status endpoint of the Neptune Loader. For more information, see Get-Status API.

The following table contains loader feed code and description.

Error or Feed Code Description


Load has been recorded but not started.


Indicates that loading is in progress and specifies the number of files currently being loaded.

When the loader parses a file, it creates one or more chunks to load in parallel. Because a single file can produce multiple chunks, the file count included with this message is usually less than the number of threads being used by the bulk load process.


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


Load has been cancelled by user.


Load has been cancelled by the system due to errors.


Load failed with an unexpected error.


Load failed as a result of one or more errors.


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.


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


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 was automatically rolled back due to deadlock.


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


The load request was not executed because its dependency check fails.


The load request has been queued up and is waiting to be executed.


The load failed because the request was invalid (for example, the specified source/bucket may not exist, or the file format is invalid).