Ingestion errors reference
Imply Lumi displays error codes to help you troubleshoot issues related to ingesting events. This topic lists common ingestion error messages and ways to resolve them. These errors can appear in the unparsable events view or your client-side application.
For more information, see Troubleshoot data ingestion.
Authentication
Authentication errors signify that you don't have the correct credentials to send events to Lumi.
| Error message | What it means | What to do |
|---|---|---|
Token is required | The IAM key token is missing from the request. | Verify that you supplied the IAM key token. |
Invalid token | The IAM key token is invalid. | Verify that your IAM key token is correct. |
Missing \"[integration]\" key from IAM key attributes | The IAM key isn't enabled for the integration. | Edit the key to add the integration. |
Missing or empty fields
If your data forwarding request doesn't include event information, Lumi returns one of the following errors.
| Error code | What it means | What to do |
|---|---|---|
EventFieldCannotBeBlank | The event field is empty. | Verify that your event field contains valid data. Make sure that the event field isn't an empty string, null, or whitespace. |
EventFieldRequired | The event field is missing. | Verify that your payload includes an event field. The event field is required and must contain valid data. |
Invalid data format
Lumi returns one of the following errors when it can't parse the structure of your raw data.
| Error code | What it means | What to do |
|---|---|---|
InvalidDataFormat | Event structure or field types don't match the expected schema. | Make sure that your event fields use the correct data types. For details on the Lumi event structure, see Event model. |
InvalidJsonPayload | The JSON payload is invalid. | Make sure that your JSON is correctly formatted. Address any formatting issues, such as missing brackets, trailing commas, or other syntax, before resending the event. |
ErrorInHandlingIndexedFields | Lumi encountered a problem processing the fields object in the submitted event. | Make sure that the fields value is a flat JSON object. Nested objects and arrays are unsupported. |