Error Stream

Overview

All errors are displayed on the Error Stream page by count, type, sources, and occurrence times.

View Errors

To view errors:

  1. Click Errors from the main menu, then the Error Stream page displays.
  2. Use the scroll down to select the time period for the errors from the number of days list.
1365

Error Stream

  1. Click any of the errors to view the error detail.
1365

Error Details

  1. Click the + sign next to an error to see the error trend.
1339

Error Trend

List of Errors

The list of errors consists of:

ErrorDescriptionPossible Action
Mandatory event property not passed; violation handler dropped eventEvent property was declared as mandatory for the said event in the schema. Incoming data did not have the mandatory event property, hence, the event was dropped.
  1. Fix the incoming data from SDK/API to ensure the said. event property is always passed
  2. Remove the validation for the said event from the schema.
Undefined event found and droppedWhen schema was published, Undefined Data Handling was set to drop the event. When an event came in for the account which was not defined in the schema, it was dropped.
  1. If the event is valid, define the said event in the schema along with its properties; data will start flowing in.
Undefined event found and acceptedWhen schema was published, Undefined Data Handling was set to allow event. When an event came in for the account which was not defined in the schema, it was accepted leading to polluted data.
  1. If the event is not valid, discard the said event in the schema.
  2. Set data handling to drop undefined events to ensure data sanity.
Undefined event property found and event droppedWhen schema was published, Undefined Data Handling was set to drop event when an undefined event property is identified. When an event property came in for the account which was not defined in the schema, the entire event was dropped.
  1. If the event property is valid, define the said property in the schema. Event along with the property will start flowing in.
Undefined event property found and event property droppedWhen schema was published, Undefined Data Handling was set to drop the said event property when an undefined event property is identified. When an event property came in for the account which was not defined in the schema, the event property was dropped.
  1. If the event property is valid, define the said property in the schema. Event property will start flowing in.
Undefined event property found and event property acceptedWhen schema was published, Undefined Data Handling was set to accept the said event property when an undefined event property is identified. When an event property came in for the account which was not defined in the schema, the event property was accepted, leading to polluted data.
  1. If the event property is not valid, discard the said event property in the schema.
  2. Set data handling to drop undefined event properties to ensure data sanity.
Mismatched event property data type found and event droppedIn the schema, the data type for event property was defined. The incoming data did not follow the defined data type. The data type fallback definition was to drop the event.
  1. Update the data type fallback definition to allow the event.
  2. Update the data coming from API/SDK to the correct data type.
Mismatched event property data type found and event property droppedIn the schema, the data type for event property was defined. The incoming data did not follow the defined data type. The data type fallback definition was to drop the event property.
  1. Update the data type fallback definition to allow the event property.
  2. Update the data coming from API/SDK to the correct data type.
Mismatched event property data type found and event acceptedIn the schema, the data type for event property was defined. The incoming data did not follow the defined data type. The data type fallback definition was to allow the event.
  1. Update the data coming from API/SDK to the correct data type.
Maximum event properties for event exceededEvent property limit of 256 for the event exceeded. Properties outside the limit dropped.
  1. Remove unwanted properties from the event.
Maximum event limit exceeded due to undefined eventsEvent limit for the project exceeded. Events outside the limit dropped.
  1. Remove unwanted events from the project.
Event property defined but not used in the last three monthsNo instance of a defined event property in the schema found in a 90-day period.
  1. Validate incoming data from SDK/API to ensure event is configured correctly.
Unaccepted characters found in event property valuesIllegal characters found in the event property value.
  1. Remove the illegal characters from API/SDK configuration.
Unaccepted characters found in event property keys for undefined eventsIllegal characters found in the event property key.
  1. Remove the illegal characters from API/SDK configuration.
No event found in last three monthsNo instance of a defined event in the schema found in a 90-day period.
  1. Validate incoming data from SDK/API to ensure event is configured correctly.
Undefined user property found and droppedWhen schema was published, Undefined Data Handling was set to drop user property when undefined. When a user property came in for the account which was not defined in the schema, the same was dropped.
  1. If the user property is not valid, discard the said event in the schema.
  2. Set data handling to drop undefined user properties to ensure data sanity.
Undefined user property found and acceptedWhen schema was published, Undefined Data Handling was set to allow user property when undefined. When a user property came in for the account which was not defined in the schema, the same was accepted.
  1. If the user property is not valid, discard the said user property in the schema.
  2. Set data handling to drop undefined user properties to ensure data sanity.
Mismatched and user property data type found and droppedIn the schema, the data type for user property was defined. The incoming data did not follow the defined data type. The data type fallback definition was to drop the user property.
  1. Update the data type fallback definition to allow the user property.
  2. Update the data coming from API/SDK to the correct data type.
Mismatched user property data type found and acceptedIn the schema, the data type for user property was defined. The incoming data did not follow the defined data type. The data type fallback definition was to accept the user property.
  1. Update the data coming from API/SDK to the correct data type.
Unaccepted characters found for user property valuesIllegal characters found in the user property value.
  1. Remove the illegal characters from API/SDK configuration.
Unaccepted characters in user profile property keyIllegal characters found in the user property key.
  1. Remove the illegal characters from API/SDK configuration.
Maximum characters exceeded for user property valueUser property limit for the project exceeded. User Properties outside the limit dropped.
  1. Remove unwanted user properties from the project.