Troubleshoot import validation and execution

Product Zbix CRM · Version 1.2.0 · Source reviewed · Reviewed 28 October 2026
Audience Administrators and implementation teams · Deployment All supported models

Overview

Import Jobs stages CSV/XLSX source data, maps columns, validates a preview and requires explicit confirmation before writing CRM records. Validation creates no CRM records. Execution commits bounded batches, so cancellation or a later error does not undo rows already imported. Retry resumes interrupted work; it does not blindly rerun successful rows.

Purpose

Use this guide to resolve invalid previews, stalled jobs and partial outcomes without duplicating records.

Prerequisites

• The original uploader or another user with the required scoped job access and action permissions.

• A retained source file and the intended target module: Leads, Accounts, Contacts or Products.

Procedure

1. Open Administration > Import Jobs and inspect the job phase, processed counts and safe error. Determine whether it is parsing, mapping, validating, awaiting confirmation or importing.

2. If mapping is incomplete, map only supported target fields and select the intended duplicate handling. Validate again and review the current generation.

3. Review invalid and duplicate rows before confirming. Download error report CSV when available and correct the source rather than ignoring rejected relationships or required fields.

4. If confirmation is stale, refresh and validate the latest mapping. Changing mapping invalidates the previous preview token.

5. For a stalled or failed job, inspect worker health and current uploader permissions. Use Retry only for interrupted failed/cancelled work that the interface allows.

6. For completed row failures, prepare a corrected new file containing the intended unresolved rows. Reconcile created, updated, skipped and failed counts before another import.

Expected result

The import has a reviewed preview or a reconciled execution outcome, with committed records and failed rows clearly distinguished.

Important notes

• Background jobs cap at 10,000 rows and 50 columns; the upload byte limit defaults to 10 MiB. Legacy synchronous imports retain a 1,000-row limit.

• XLSX formulas, error cells, macros, external links and unsafe archive content are rejected. Store dates as ISO date text.

• Mapping becomes immutable after execution starts. Cancellation waits for the active bounded batch and stops later batches.

• A repeated upload of the same source can return the existing job; this prevents accidental recreation.

Troubleshooting

• Ready preview cannot confirm: refresh after mapping changes and review the current validation result.

• Some rows imported before cancellation: reconcile the execution counts; cancellation is not rollback.

• Repeated data errors: fix the source and upload a corrected file rather than retrying unchanged failed rows.

Related articles

• Background processing and durable jobs

• API validation and safe concurrency

• Private files and generated document storage

• Prepare a safe support case