Understanding the Ingestion Log Error

What the ingestion log is

The ingestion log is a diagnostic view surfaced from the source report. When Zeotap processes a file or a record from a source, any record that cannot be parsed, typed, or converted is recorded in the log with an error title and a description. Reading the log tells you which records were rejected and what to change in the source data — a field format, a data type, or a time unit — before you re-ingest.

Prerequisites

Before you review the ingestion log, confirm that the source has completed at least one ingestion attempt and that its source report has generated. You need permission to view source reports for the source you are investigating.

Read the ingestion log

Open the source report for the source you are investigating and locate the ingestion log view. The log lists errors grouped by category. Each entry names an error title and a description that identifies the failing column and the observed value.

Error categories

Zeotap classifies known ingestion errors into the categories below. Match the error title in your log to the row here to identify the change required in your source data.

Error title	What it means	Where to look
`Parse error`	The file could not be parsed because the file format is incorrect.	The whole file — verify delimiter, encoding, and header row against the source configuration.
`Invalid Type Error`	A column value does not match the declared type. Example: `Invalid type String of the event_timestamp column. It must be of type Long or String.`	The named column in the source file — cast the value to the expected type before ingestion.
`Invalid Timestamp Format`	A timestamp value does not match the format configured for the column. Example: `Value 22-03-2022 for column event_timestamp is not in the expected format of dd/MM/yyyy.`	The named column in the source file — reformat the timestamp to the configured pattern (for example, `dd/MM/yyyy`).
`Type Conversion Error`	A `set-type` transformation could not convert a column value to the target type. Example: `Error encountered while executing 'set-type' : Column 'age' cannot be converted to a 'double'.`	The named column in the source file — non-numeric values (blanks, text, symbols) in a numeric column trigger this.
`Others`	A miscellaneous condition that does not fit the categories above. Example: the time unit specified for a timestamp is not supported. The supported time units are `MICROSECONDS`, `SECONDS`, and `MILLISECONDS`.	The error description text — it names the specific field or configuration at fault.

Fix the source data

Use the error title and the description together to locate the offending column and record in the source file. The description names the column, the observed value, and the expected format or type.

Fix a timestamp format mismatch

If the log shows Invalid Timestamp Format, reformat the values in the affected column to match the pattern configured on that column. For a column configured as dd/MM/yyyy, a well-formed CSV extract looks like:

user_id,event_timestamp
u_10001,22/03/2022
u_10002,23/03/2022

A value written as 22-03-2022 (hyphen-separated) in the same column raises Value 22-03-2022 for column event_timestamp is not in the expected format of dd/MM/yyyy. and is rejected.

Fix an unsupported time unit

If the log shows an Others entry stating that the time unit is not supported, set the time unit on the affected timestamp column to one of MICROSECONDS, SECONDS, or MILLISECONDS. Any other value is rejected.

Fix a type mismatch on `event_timestamp`

If the log shows Invalid type String of the event_timestamp column. It must be of type Long or String., cast the column values to Long (an epoch integer) or String (a formatted timestamp) before ingestion. Any other declared type is rejected for this column.

Fix a type conversion failure

If the log shows Error encountered while executing 'set-type' : Column 'age' cannot be converted to a 'double'. — or the same message for another column such as loyalty_points — inspect the column for values that are not parseable as the target type: blank cells, text, commas, currency symbols, or thousands-separators. Clean the source column and re-ingest.

Fix a parse error

If the log shows Parse error, the file itself failed to parse against the source configuration. Verify the delimiter, encoding, header row, and quoting of the file against the source configuration, correct the file, and re-ingest.

Verify the fix

Re-ingest the corrected file or record from the source and open the source report for the new run. The ingestion log for the new run should no longer list the corrected error title against the same column, and the record counts in the source report should account for the previously-rejected records.

When to contact support

Contact support if:

The ingestion log shows an error title that is not listed in the table above.
You have corrected the source data and the same error title recurs against the same column in a fresh run.
The Parse error category recurs after you have confirmed the file format matches the source configuration.

Include in your request: the source name, the identifier of the source report for the failed run, the exact error title and description text from the ingestion log, and a small sample of the source file (with sensitive fields removed) showing the affected column and value.

FAQ

Which time units are accepted for timestamp columns?

Zeotap accepts MICROSECONDS, SECONDS, and MILLISECONDS as time units for timestamp columns. Any other value produces an entry in the Others category of the ingestion log stating that the time unit is not supported.

What type does event_timestamp need to be?

The event_timestamp column must be of type Long or String. A value declared as any other type produces an Invalid Type Error with the message Invalid type String of the event_timestamp column. It must be of type Long or String.

Why does a numeric column fail with a Type Conversion Error?

A set-type transformation to a numeric type such as double fails when the column contains values that are not parseable as a number — blank cells, text, currency symbols, or thousands-separators. The log names the column, for example Column 'age' cannot be converted to a 'double'. or Column 'loyalty_points' cannot be converted to a 'double'. Clean the source column and re-ingest.

Does a Parse error reject the whole file or just some records?

A Parse error is raised while parsing the file itself because of incorrect file format, so the failure applies at the file level rather than at the individual-record level. Fix the file format and re-ingest.

Next steps

Explore Snowflake source error handling → Error Handling and More
Explore Journey error codes → Journey Error Codes
Explore Journey error resolution → Resolve Journey Errors
Explore more CDP topics → What’s Next

​What the ingestion log is

​Prerequisites

​Read the ingestion log

​Error categories

​Fix the source data

​Fix a timestamp format mismatch

​Fix an unsupported time unit

​Fix a type mismatch on event_timestamp

​Fix a type conversion failure

​Fix a parse error

​Verify the fix

​When to contact support

​FAQ

​Next steps

What the ingestion log is

Prerequisites

Read the ingestion log

Error categories

Fix the source data

Fix a timestamp format mismatch

Fix an unsupported time unit

Fix a type mismatch on `event_timestamp`

Fix a type conversion failure

Fix a parse error

Verify the fix

When to contact support

FAQ

Next steps