Bulk Import -- Error Handling

Bulk Import errors are tracked at the row level and never block unrelated rows from being processed.

NOTE

A single row-level error does not fail the import. This is expected behavior for large imports. Operators are not required to restart or reschedule the import due to errors. Failed rows can be:

• Ignored during execution
• Corrected manually after completion

Errors can occur during both the dry run phase and the final execution phase.

Error Scope

• Errors are always associated with a specific row
• Errors never invalidate the entire import automatically
• Structural validation errors block execution
• Data-level errors only affect the failing rows

Dry Run Errors

Dry run errors represent issues detected during simulated execution.

Typical causes:

• Invalid data types
• Invalid date or time formats
• Unresolvable identifiers
• Missing required columns
• Relation resolution failures

Dry run errors:

• Are fully downloadable as structured error files
• Do not prevent scheduling
• Must be manually reviewed and accepted or corrected

Execution Errors

Execution errors occur during the live import phase.

Characteristics:

• Only affect failing rows
• Do not rollback successful rows
• May differ from dry run errors due to live data changes

Error Persistence

• Errors are persisted with the import job
• Error reports can be downloaded after both dry run and execution
• Errors are not automatically cleared

Operational Implications

• There is no automatic retry mechanism
• Failed rows must be corrected and re-imported manually
• Successful rows are never reprocessed automatically