

For similar capabilities to Amazon Timestream for LiveAnalytics, consider Amazon Timestream for InfluxDB. It offers simplified data ingestion and single-digit millisecond query response times for real-time analytics. Learn more [here](https://docs.amazonaws.cn//timestream/latest/developerguide/timestream-for-influxdb.html).

# Troubleshooting
<a name="Troubleshooting"></a>

This section contains information on troubleshooting Timestream for LiveAnalytics. 

**Topics**
+ [Handling WriteRecords throttles](troubleshoot-writethrottles.md)
+ [Handling rejected records](troubleshoot-rejectedrecords.md)
+ [Troubleshooting UNLOAD from Timestream for LiveAnalytics](troubleshoot-export-unload.md)
+ [Timestream for LiveAnalytics specific error codes](APITimestreamSpecificErrors.md)

# Handling WriteRecords throttles
<a name="troubleshoot-writethrottles"></a>

Your memory store write requests to Timestream may be throttled as Timestream scales to adapt to the data ingestion needs of your application. If your applications encounter throttling exceptions, you must continue to send data at the same (or higher) throughput to allow Timestream to automatically scale to your application's needs. 

Your magnetic store write requests to Timestream may be throttled if the maximum limit of magnetic store partitions receiving ingestion. You will see a throttle message directing you to check the `ActiveMagneticStorePartitions` Cloudwatch metric for this database. This throttle may take up to 6 hours to resolve. To avoid this throttle, you should use the memory store for any high throughput ingestion workload. For magnetic store ingestion, you can target ingesting into fewer partitions by limiting how many series and the time duration that you ingest into

For more information about data ingestion best practices, see [Writes](data-ingest.md).

# Handling rejected records
<a name="troubleshoot-rejectedrecords"></a>

If Timestream rejects records, you will receive a `RejectedRecordsException` with details about the rejection. Please refer to [Handling write failure](https://docs.amazonaws.cn/timestream/latest/developerguide/code-samples.write.html#code-samples.write.rejectedRecordException) for more information on how to extract this information from the WriteRecords response.

 All rejections will be included in this response **with the exception of updates to the magnetic store where the new record's version is less than or equal to the existing record's version**. In this case, Timestream will not update the existing record that has the higher version. Timestream will reject the new record with lower or equal version and write these errors asynchronously to your S3 bucket. In order to receive these asynchronous error reports, you should set the `MagneticStoreRejectedDataLocation` property in `MagneticStoreWriteProperties` on your table. 

# Troubleshooting UNLOAD from Timestream for LiveAnalytics
<a name="troubleshoot-export-unload"></a>

Following is guidance for troubleshooting related to the UNLOAD command.

[\[See the AWS documentation website for more details\]](http://docs.amazonaws.cn/en_us/timestream/latest/developerguide/troubleshoot-export-unload.html)

# Timestream for LiveAnalytics specific error codes
<a name="APITimestreamSpecificErrors"></a>

This section contains the specific error codes for Timestream for LiveAnalytics. 

## Timestream for LiveAnalytics write API errors
<a name="APITimestreamSpecificErrors.write"></a>

****InternalServerException****  
 HTTP Status Code: 500

**ThrottlingException**  
 HTTP Status Code: 429

**ValidationException**  
 HTTP Status Code: 400

**ConflictException**  
 HTTP Status Code: 409

**AccessDeniedException**  
You do not have sufficient access to perform this action.  
 HTTP Status Code: 403

**ServiceQuotaExceededException**  
 HTTP Status Code: 402

**ResourceNotFoundException**  
 HTTP Status Code: 404

**RejectedRecordsException**  
 HTTP Status Code: 419

**InvalidEndpointException**  
 HTTP Status Code: 421

## Timestream for LiveAnalytics query API errors
<a name="APITimestreamSpecificErrors.query"></a>

**ValidationException**  
 HTTP Status Code: 400

**QueryExecutionException**  
 HTTP Status Code: 400

**ConflictException**  
 HTTP Status Code: 409

**ThrottlingException**  
 HTTP Status Code: 429

**InternalServerException**  
 HTTP Status Code: 500

**InvalidEndpointException**  
 HTTP Status Code: 421