Data Warehouse and Storage Import Monitoring and Error Guide

This guide explains every error that can appear on the Monitoring screen of a data warehouse (Snowflake, BigQuery, Databricks) and Amazon S3 import integration: what each error means, what happens to your data, why it happens, and how to fix it.

This guide covers imports only. Export integrations do not produce these errors.

How to read the monitoring screen

Each import run is summarized on the Monitoring screen:

• Success rate: the percentage of your data that was successfully ingested. It is calculated per cell (individual mapped values), not per row: successful cells ÷ total cells. An invalid value in one column does not cause the other mapped values in the same row to fail.

• Error list: the errors found in the run, grouped by type, with a count for each. You can open a run to see the detailed breakdown.

• Columns that are never counted as errors: the cursor/timestamp column used to detect new data, and any column in your source that you did not map, are ignored. They are not shown as errors and do not lower your success rate.

Data errors

IdentifierIdentityRejected

• What it means: The record's identifiers could not be resolved to a single user: they point to more than one existing user.

• What happens to your data: The affected update is skipped. It is reported as partial, not a full failure.

• Why it happens: When you map more than one identifier, their values in the same row describe different people (for example, the mapped email belongs to one existing user and the mapped user ID to another).

• How to fix it: Make sure every identifier in a row belongs to the same person. When you map multiple identifiers, their combination must consistently identify one user. (This is the identity-resolution form of IdentifierConflict.)

EventIdentityLookupFailed

• What it means: The event could not be attached to a user because identity resolution failed for the record.

• What happens to your data: The affected event is skipped (reported as partial).

• Why it happens: This error has the same root cause as IdentifierIdentityRejected: the record's identifiers resolve to more than one user, so the event cannot be associated with a single user. The two errors usually appear together on the same record.

• How to fix it: Fix the conflicting identifiers so each row identifies exactly one user.

IdentifierIdentityRejected and EventIdentityLookupFailed appear together. They are the two halves of the same problem: an identity conflict on one record. IdentifierIdentityRejected is raised on the attribute/identifier lane and EventIdentityLookupFailed on the event lane, so a single conflicting record produces both (equal counts). Treat them as one issue and fix the conflicting identifiers.

NoIdentifier

• What it means: The record has no identifier value, so Insider One cannot determine which user it belongs to.

• What happens to your data: The whole record is skipped.

• Why it happens: The mapped identifier column is empty, null, or missing for that row.

• How to fix it: Make sure every row has a non-empty value in the column mapped as the identifier (for example, email, phone, or your user ID).

InvalidIdentifier

• What it means: The identifier value is present but not in a valid format.

• What happens to your data: The whole record is skipped.

• Why it happens: The value doesn't match the expected format for its identifier type (for example, an email that isn't a valid email address or a malformed phone number).

• How to fix it: Clean the identifier values in your source so they match the expected format (valid email, correctly formatted phone number, etc.).

IdentifierConflict

• What it means: The identifiers in a single record point to more than one user, or conflict with each other.

• What happens to your data: The whole record is skipped.

• Why it happens: When more than one identifier is mapped, their values in the same row do not consistently describe one user.

• How to fix it: Ensure the identifier values in each row belong to the same person. When you map multiple identifiers, their combination must uniquely and consistently identify one user.

IdentifierIdentityReset

• What it means: The user's identity was reset with no forward target, so this update could not be applied.

• What happens to your data: The affected update is skipped (partial).

• Why it happens: This usually occurs temporarily after an identity merge or reset.

• How to fix it: Re-sync the affected users after the merge settles. If it persists, escalate to the Insider One team.

EventIdentityRefreshFailed

• What it means: Refreshing the user's identity for this event failed.

• What happens to your data: The affected event is skipped (partial).

• Why it happens: An identity conflict or a transient identity-service error.

• How to fix it: Fix conflicting identifiers; resync the affected data if the issue was temporary.

IdentifierLimitBlock

• What it means: The per-user identifier limit was reached; one identifier was dropped.

• What happens to your data: The record is written, but one identifier (which one depends on partner config) is not stored.

• Why it happens: Too many identifiers are mapped/sent for a single user.

• How to fix it: Reduce the number of identifiers mapped per user.

InvalidPhone

• What it means: The phone identifier is not in a valid format.

• What happens to your data: The whole record is skipped.

• Why it happens: The phone value does not match the expected format.

• How to fix it: Clean phone values to a valid format (E.164, for example +905551112233).

InvalidTimestamp

• What it means: The record-level timestamp could not be read.

• What happens to your data: The whole record is skipped.

• Why it happens: The timestamp does not match the expected format.

• How to fix it: Use ISO 8601 (YYYY-MM-DD HH:MM:SS) or a Unix timestamp.

InvalidInsiderId

• What it means: The value mapped to insider_id is not a valid Insider ID.

• What happens to your data: The whole record is skipped.

• Why it happens: The mapped column contains malformed Insider IDs.

• How to fix it: Provide a valid insider_id in the mapped column, or map identifiers instead.

NoEventAndAttribute

• What it means: The record contains neither a valid event nor any attribute value: there is nothing to import.

• What happens to your data: The whole record is skipped.

• Why it happens: Every mapped payload field is empty for that row, or the mapping does not point to any populated column.

• How to fix it: Make sure each row carries at least one valid event or one attribute value, and that your mapping points to columns that actually contain data.

AttributePaused

• What it means: The attribute is currently paused in your integration settings, so its data is intentionally not imported.

• What happens to your data: That field is skipped for all records.

• Why it happens: The attribute was toggled off in the integration's attribute settings.

• How to fix it: If you want this data imported, unpause the attribute in the integration's Attributes settings.

AttributeNotEligible

• What it means: The attribute is not eligible to be imported for this integration.

• What happens to your data: That field is skipped for all records.

• Why it happens: The attribute is not enabled/eligible in your account configuration for this import type.

• How to fix it: Confirm the attribute is eligible in your configuration, or map the field to an eligible attribute instead.

InvalidAttribute

• What it means: The attribute values fail validation.

• What happens to your data: That field is skipped for the affected records.

• Why it happens: The values do not conform to the attribute's rules (wrong type after normalization, or values that break validation).

• How to fix it: Correct the values in your source so they match the attribute's expected type and constraints.

AttributeColumnTypeMismatch

• What it means: The value's type clashed with the existing column's type for that attribute.

• What happens to your data: That attribute is skipped for the affected records; the rest of the record is written.

• Why it happens: A column already stored one type (for example, number) and a different type (for example, string) arrived. (Per-record variant of the integration-level MappingMismatchingDataType.)

• How to fix it: Cast the value at the source to the attribute's existing type, or remap to a compatible attribute.

InvalidObjectAttribute

• What it means: An object attribute value failed validation.

• What happens to your data: That attribute is skipped for the affected records.

• Why it happens: The object's structure or a field type does not match the attribute schema.

• How to fix it: Make the object structure and field types match the attribute schema.

AttributeObjectArrayOverflow

• What it means: An object-array attribute went over its maximum item count.

• What happens to your data: That attribute is skipped for the affected records.

• Why it happens: The array exceeded the size cap (50 items).

• How to fix it: Keep object-array attributes within the cap.

AttributeObjectArrayRestrictionExceeded

• What it means: An object-array attribute violated its configured restriction.

• What happens to your data: That attribute is skipped for the affected records.

• Why it happens: The array exceeded a size/shape restriction defined for the attribute.

• How to fix it: Reduce items or align with the restriction.

AttributeRequiredFieldMissing

• What it means: A required field for the attribute was missing.

• What happens to your data: That attribute is skipped for the affected records.

• Why it happens: The mapping marks a field as required, but the source row did not provide it.

• How to fix it: Provide the required field, or review whether it should be required.

AttributeDynamoItemSize

• What it means: The attribute exceeded the maximum storage item size (400 KB).

• What happens to your data: That attribute is skipped for the affected records.

• Why it happens: The attribute value/payload is too large.

• How to fix it: Reduce the size of the attribute value at the source.

CustomAttrCheckFailed

• What it means: A custom-attribute validation rule failed.

• What happens to your data: That attribute is skipped for the affected records.

• Why it happens: The value did not satisfy the custom attribute's rule.

• How to fix it: Correct the value to match the custom attribute's rule.

KeyNotInMapping

• What it means: (Amazon S3 only) An object in an array-of-object field contains a key that is not part of the attribute's mapping.

• What happens to your data: The unexpected key is skipped; the rest of the object is imported.

• Why it happens: The JSON objects in your array contain keys that aren't defined in the array-of-object attribute schema.

• How to fix it: Make the keys in your source objects match the attribute schema: remove unexpected keys, or add them to the mapping.

NumberParsing

• What it means: A value mapped to a numeric attribute could not be read as a number.

• What happens to your data: That field is skipped for the affected records.

• Why it happens: The value contains characters that aren't valid in a number (letters, symbols, thousands separators, currency signs, blanks).

• How to fix it: Make sure values mapped to number attributes are clean numeric values.

  • Snowflake / BigQuery / Databricks: cast or clean the column in your query (for example, remove currency symbols/commas, TRY_CAST to a numeric type) so it returns plain numbers.

  • S3: ensure the values in the file are plain numbers (no currency or thousands separators).

TimestampParsing

• What it means: A value mapped to a timestamp attribute could not be read as a valid timestamp.

• What happens to your data: That field is skipped for the affected records.

• Why it happens: The value does not match the timestamp format the integration expects.

• How to fix it: Reformat the value to a recognized timestamp (ISO 8601, for example YYYY-MM-DD HH:MM:SS, or a Unix timestamp) that matches the format configured on the integration.

  • Snowflake / BigQuery / Databricks: confirm the column is a genuine timestamp type, or format it to the expected string in your query.

  • S3: ensure the file's timestamp values use the configured format.

DateTimeParsing

• What it means: A value mapped to a datetime attribute could not be read as a valid date/time.

• What happens to your data: That field is skipped for the affected records.

• Why it happens: The date/time value does not match the expected format.

• How to fix it: Reformat the value to match the integration's configured date/time format. (Same platform guidance as TimestampParsing above.)

ValueTooLong

• What it means: A text value is longer than the maximum allowed length.

• What happens to your data: That field is skipped for the affected records.

• Why it happens: The string exceeds the attribute's length limit.

• How to fix it: Shorten or truncate the value in your source so it fits within the limit.

InvalidEventName

• What it means: The event name is not a recognized event.

• What happens to your data: The affected event values are skipped.

• Why it happens: The event name has a typo or is not defined in your event catalog.

• How to fix it: Check the event name in your source against your valid event names, and correct the typo or define the event. (The monitoring screen links to the relevant help article to find valid event names.)

InvalidEvent: EventParamInvalid

• What it means: An event parameter is missing or invalid.

• What happens to your data: The affected event is skipped.

• Why it happens: A parameter the event needs is absent or fails validation.

• How to fix it: Make sure all required event parameters are present and valid. The error detail names the parameter that caused the problem.

InvalidEvent: TimestampInvalid

• What it means: The event's timestamp could not be read.

• What happens to your data: The affected event is skipped.

• Why it happens: The event timestamp does not match the expected format.

• How to fix it: Reformat the event timestamp to match the integration's configured format (ISO 8601 or Unix timestamp).

FieldIsRequiredForEvent

• What it means: A required parameter for the event is missing.

• What happens to your data: The affected event is skipped.

• Why it happens: The mapping marks a parameter as required, but the source row does not provide it.

• How to fix it: Add the missing required parameter to your source data, or review whether it should be required in the mapping. The error detail names the missing parameter.

When an event has more than one invalid required parameter (for example both quantity and currency for purchase event), only one error is reported at a time: whichever parameter is checked first, which is not deterministic. After you fix that one, a different parameter error may appear on the next run. Review all of an event's parameters together rather than fixing them one at a time.

EventBlocked

• What it means: The event is on the account's blocked list.

• What happens to your data: The event is skipped; the rest of the record still imports.

• Why it happens: The event name is blocked for your account.

• How to fix it: Remove the event from the block list, or stop sending it.

TopkBlockedEvent

• What it means: The account's TopK event limit was reached.

• What happens to your data: The event is skipped.

• Why it happens: Too many distinct event names for the account's TopK limit.

• How to fix it: Reduce the number of distinct events or request a higher limit.

TopkBlockedAttribute

• What it means: The account's TopK attribute limit was reached.

• What happens to your data: That attribute is skipped; the rest of the record still imports.

• Why it happens: Too many distinct attribute names for the account's TopK limit.

• How to fix it: Reduce the number of distinct attributes or request a higher limit.

NsqSizeExceededEvent

• What it means: The event is too large for the processing message bus.

• What happens to your data: The event is skipped.

• Why it happens: The event payload exceeds the message-size limit.

• How to fix it: Reduce the event payload size (fewer/smaller parameters).

NsqSizeExceededAttribute

• What it means: The attribute message is too large for the processing message bus.

• What happens to your data: That attribute is skipped.

• Why it happens: The attribute payload exceeds the message-size limit.

• How to fix it: Reduce the attribute value size.

EventDynamoItemSize

• What it means: The event exceeded the maximum storage item size (350 KB).

• What happens to your data: The event is skipped.

• Why it happens: The event payload is too large.

• How to fix it: Reduce the event payload size.

EventParamUnsupportedType

• What it means: An event parameter had an unsupported type.

• What happens to your data: That parameter is skipped; the event still imports.

• Why it happens: The parameter value's type is not supported for that parameter.

• How to fix it: Send the parameter in a supported type.

EventParamUnsupported

• What it means: An event parameter is not supported.

• What happens to your data: That parameter is skipped; the event still imports.

• Why it happens: The parameter is not recognized/allowed for this event.

• How to fix it: Remove or remap the parameter.

EventParamBlocked

• What it means: An event parameter is on the block list.

• What happens to your data: That parameter is skipped; the event still imports.

• Why it happens: The parameter is blocked for your account.

• How to fix it: Remove it from the block list, or stop sending it.

NullEvent

• What it means: The event object was empty/null.

• What happens to your data: The event is skipped.

• Why it happens: An event entry with no content was produced by the mapping.

• How to fix it: Ensure mapped event rows carry a valid event.

EventNameEmpty

• What it means: The event name was empty.

• What happens to your data: The event is skipped.

• Why it happens: The column mapped to the event name was empty for that row.

• How to fix it: Make sure every event row has a non-empty event name.

An event that is dropped because it falls outside the allowed time-to-live (TTL) window is not shown as a line error on the monitoring screen. If some events are missing but you do not see a matching error, check whether their timestamps are older than the allowed time window.

Duplicate data (Action required)

This error is not raised during a sync. Insider One compares your integration's last two syncs and measures how many rows were sent again with identical content.

DWH_DUPLICATE_DATA_THRESHOLD_EXCEEDED

What it means: More than 5% of the rows in your last two syncs were resent with identical content, so the integration was moved to Action required. Exactly 5% or below does not trigger it. The integration shows the figures, for example: 40.00% of the rows sent in the last two syncs were duplicates (8 of 20).

What happens to your data: Nothing already imported is lost, and user attributes are unaffected, but resent event rows can create duplicate events. No new data is imported until you resolve the error.

Why it happens: Your source query returns rows that have not changed: usually a cursor column (for example updated_at) refreshed on every export, a full-table export scheduled as an incremental sync, or a view rebuilt on each run.

How to fix it:

1. In your source platform, make the query return only the rows that changed since the last sync.

2. Open the integration in Insider One and set its status back to Active. The error is cleared and syncing resumes. If the ratio is still above 5% at the next check, move the integration back to Action required.

Which integrations are checked: This check applies to Snowflake, Google BigQuery, and Databricks import integrations only while their status is Active. Integrations created before this check was released are not affected. Amazon S3 integrations are not included. An integration that has synced only once also cannot be checked because no previous sync is available for comparison.

Failed syncs (Action required)

When a sync has a Failed status, it never started: it stopped on an integration-level problem, not a data issue, and imported nothing, so its Success Rate shows N/A. The integration moves to Action required and stays interrupted until you resolve the cause. Open the sync's Errors tab to see exactly which error it hit, fix it at the source platform (not in the data), then resume the sync.

The most common causes are:

• A permission was revoked: Insider can no longer read your source.

  • Snowflake: re-grant the role's privileges on the warehouse/database/schema.

  • BigQuery / GCS: restore the service account's IAM roles in the Google Cloud Console.

  • Databricks: restore the token/service-principal Unity Catalog grants.

  • S3: restore the bucket policy / IAM permissions.

  • Azure Blob: restore the connection string or RBAC role.

• Change tracking was disabled, or the stream became stale (Snowflake Streams / Databricks Change Data Feed): re-create or re-enable change tracking so incremental syncs can resume.

• A mapped identifier column was dropped: restore the column or update the mapping.

Quick reference