Troubleshoot issues writing data

Learn how to avoid unexpected results and recover from errors when writing to InfluxDB Cloud Serverless.

• Handle write responses
  • Review HTTP status codes
• Troubleshoot failures
• Troubleshoot rejected points

Handle write responses

InfluxDB Cloud Serverless does the following when you send a write request:

1. Validates the request.

2. If successful, attempts to ingest data from the request body; otherwise, responds with an error status.

3. Ingests or rejects data from the batch and returns one of the following HTTP status codes:

   • 204 No Content: All of the data is ingested and queryable.
   • 400 Bad Request: Some or all of the data has been rejected. Data that has not been rejected is ingested and queryable.

   The response body contains error details about rejected points, up to 100 points.

Writes are synchronous–the response status indicates the final status of the write and all ingested data is queryable.

To ensure that InfluxDB handles writes in the order you request them, wait for the response before you send the next request.

Review HTTP status codes

InfluxDB uses conventional HTTP status codes to indicate the success or failure of a request. The message property of the response body may contain additional details about the error. InfluxDB Cloud Serverless returns one the following HTTP status codes for a write request:

The message property of the response body may contain additional details about the error. If your data did not write to the bucket, see how to troubleshoot rejected points.

Troubleshoot failures

If you notice data is missing in your database, do the following:

• Check the HTTP status code in the response.
• Check the message property in the response body for details about the error.
• If the message describes a field error, troubleshoot rejected points.
• Verify all lines contain valid syntax (line protocol).
• Verify the timestamps in your data match the precision parameter in your request.
• Minimize payload size and network errors by optimizing writes.

Troubleshoot rejected points

When writing points from a batch, InfluxDB rejects points that have syntax errors or schema conflicts. If InfluxDB processes the data in your batch and then rejects points, the HTTP response body contains the following properties that describe rejected points:

• code: "invalid"
• line: the line number of the first rejected point in the batch.
• message: a string that contains line-separated error messages, one message for each rejected point in the batch, up to 100 rejected points.

InfluxDB rejects points for the following reasons:

• a line protocol parsing error
• an invalid timestamp
• a schema conflict

Schema conflicts occur when you try to write data that contains any of the following:

• a wrong data type: the point falls within the same partition (default partitioning is measurement and day) as existing bucket data and contains a different data type for an existing field
• a tag and a field that use the same key

Example

The following example shows a response body for a write request that contains two rejected points:

{
  "code": "invalid",
  "line": 2,
  "message": "failed to parse line protocol:
              errors encountered on line(s):
              error parsing line 2 (1-based): Invalid measurement was provided
              error parsing line 4 (1-based): Unable to parse timestamp value '123461000000000000000000000000'"
}

Check for field data type differences between the rejected data point and points within the same database and partition–for example, did you attempt to write string data to an int field?