# Import queue

> Track IS Tools data imports by status: pending, running, finished, or failed. Inspect error logs to identify issues and correct your import data file.

[Imports](imports.md) > Import queue

This form displays both imports and reports that have been processed or scheduled by the current user.

Once this form is opened, observe the information of your import: the template’s name, the time it was queued at, status, amongst others. The **Status** column, indicates whether the import is finished or not. With a newly imported data file, the **Status** is shown as **Pending**. Wait for a few seconds, and click the Refresh icon now and then, to check whether the operation is finished.

> **Tip:**
> 
> Show or hide the colums you wish by clicking the ![NDMEhiddenSettings](_images/NDMEhiddenSettings.png) icon placed at the top left corner of this form. Filters may be applied per column, and then saved all together with the **Filters** button.

When the import is finished, **Status** changes to either **Finished** (if the operation was completely successful), **Finished with remarks** (if the error log contains any entry), or **Failed** (if a major error occurred).

Optionally, click on the template name, which works as hyperlink, to take you back to the import in the [Import templates](import_templates.md) form.

In case of remarks or failure, inspect the log of the import operation by clicking the icon in the **Template** column. Correct the issues pointed out by the remarks and upload the file again in the [**Prepare import run**](prepare_import_run.md) form.

> **Note:**
> 
> If a data file needs to be uploaded more than once due to _remarks_, make sure to [edit the Template type](import_templates.md#_edit_an_import_template) to a better option. For instance, **Insert or update**.

**Most common remarks in the import log**

1.  Data in Excel cells do not match with the type of field in the IS Tools application. For instance, a cell containing text that is meant to be imported into a number field, which is not supported in order to keep the integrity of the information ('_Cannot read number_'). Or a value that has not been defined in the list of a drop-down is tried to be imported into the drop-down field ('_Drop-down value not found_').

2.  '_Record already exists. This is not an UPDATE import_'. An **Insert only** import has found an existing record name in the data file.

3.  '_Record does not exist. This is not an INSERT import_'. An **Update only** import has found an non-existing record name in the data file.

4.  The data file contains formulas, formatting, macros or data is located in other sheets instead of in the first sheet only.

5.  '_B2: No value existed in record "R1" for "Field1", nothing to delete_'. Cells of the Excel file are empty and the **Skip empty cells** setting is not ticked (in the [Prepare import run](prepare_import_run.md) form).

6.  '_Could not insert value because of unique constraint_'. A cell of the Excel file contains a non-unique value, that fails to be inserted into a field set as [Unique](fields.md#unique).

7.  '_Mandatory field values cannot be deleted: Row skipped!_'. A cell of the Excel file contains an empty value, that fails to be inserted into a field set as [Mandatory](fields.md#mandatory), in combination with the **Skip empty cells** setting unticked (in the [Prepare import run](prepare_import_run.md) form).

8.  '_Some mandatory fields are missing values: Row skipped!_'. A cell of the Excel file contains an empty value, that fails to be inserted into a field set as [Mandatory](fields.md#mandatory).

9.  '_Rule invocation nested too deep_'. The row in consideration will be skipped (i.e., not imported) due to field(s) that attempted to be triggered by [recursing rules](examples_of_rules.md#recursive).

10.  '_Validation error, column(s): B. Not a valid e-mail address. Row skipped!_'. A cell of the Excel file contains an invalid value, that fails to be inserted into a field used in a [validation rule](rules_editor.md); e.g., the field "E-mail address" should validate the format [john.smith@company.com](mailto:john.smith@company.com).

11.  '_Validation error, column(s): B. Describe reason cannot be empty. Row skipped!_'. A [validation rule](rules_editor.md) using the _Is empty_ function is active.

_Delete/Cancel_ and _Terminate_ icons. Imports _can be deleted_ only if its execution has not started or has already finished (i.e., the **Status** indicates that it is still **Waiting in queue** or that is **Finished**, respectively) by ticking the corresponding checkbox in the leftmost column and clicking the **Delete** button. But if _an import is already running_ (i.e., the **Status** indicates **Started** or any percentage done), it _can be terminated_ by clicking on the Terminate icon (if [form rights](form_rights.md#_import_forms_rights) set).

> **Caution:**
> 
> Caution must be taken with the termination of an import, since this action _does not undo_ the changes made on records before the **Terminate** button was clicked. In other words, it is possible that records were already inserted, updated or deleted (depending on the import type) even if the termination action was performed.