Error Stream
Overview
All errors are displayed on the Error Stream page by count, type, sources, and occurrence times.
View Errors
To view errors:
- Click Errors from the main menu, then the Error Stream page displays.
- Use the scroll down to select the time period for the errors from the number of days list.
- Click any of the errors to view the error detail.
- Click the + sign next to an error to see the error trend.
List of Errors
The list of errors consists of:
Error | Description | Possible Action |
---|---|---|
Mandatory event property not passed; violation handler dropped event | Event 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. |
|
Undefined event found and dropped | When 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. |
|
Undefined event found and accepted | When 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. |
|
Undefined event property found and event dropped | When 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. |
|
Undefined event property found and event property dropped | When 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. |
|
Undefined event property found and event property accepted | When 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. |
|
Mismatched event property data type found and event dropped | In 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. |
|
Mismatched event property data type found and event property dropped | In 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. |
|
Mismatched event property data type found and event accepted | In 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. |
|
Maximum event properties for event exceeded | Event property limit of 256 for the event exceeded. Properties outside the limit dropped. |
|
Maximum event limit exceeded due to undefined events | Event limit for the project exceeded. Events outside the limit dropped. |
|
Event property defined but not used in the last three months | No instance of a defined event property in the schema found in a 90-day period. |
|
Unaccepted characters found in event property values | Illegal characters found in the event property value. |
|
Unaccepted characters found in event property keys for undefined events | Illegal characters found in the event property key. |
|
No event found in last three months | No instance of a defined event in the schema found in a 90-day period. |
|
Undefined user property found and dropped | When 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. |
|
Undefined user property found and accepted | When 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. |
|
Mismatched and user property data type found and dropped | In 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. |
|
Mismatched user property data type found and accepted | In 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. |
|
Unaccepted characters found for user property values | Illegal characters found in the user property value. |
|
Unaccepted characters in user profile property key | Illegal characters found in the user property key. |
|
Maximum characters exceeded for user property value | User property limit for the project exceeded. User Properties outside the limit dropped. |
|
Updated 11 months ago