> For the complete documentation index, see [llms.txt](https://support.who-umc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.who-umc.org/vigiflow/import-data/how-to-tell-why-an-import-has-failed.md).

# How to tell why an import has failed

{% hint style="warning" %}
Import functionality might need to be enabled by UMC. For assistance, [contact UMC](mailto:support@who-umc.org)
{% endhint %}

There are three different import statuses in VigiFlow. 

* **`Ok`**<mark style="background-color:$primary;">:</mark> All ICSRs contained in the file were successfully imported. &#x20;
* **`Partial`**: Some ICSRs were successfully imported but others did not meet the minimum requirements of the validation rules. In the “Number of ICSRs” column, you can view the total number of ICSRs in the report, with the successfully imported ones indicated in parentheses. &#x20;
* **`Fail`**: None of the ICSRs were imported. &#x20;

If the import of XML files has failed or partially failed, you can tell why by following these steps:  &#x20;

1. Go to the “**`List of imports`**” in VigiFlow.&#x20;
2. Click on the specific row of an imported file. &#x20;
3. In “**`Import details`**”, you can see which ICSRs failed to import and why.&#x20;

<figure><img src="https://844234868-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FD7MbxF2Gm1Bf1uqE3mOA%2Fuploads%2FMEuhb8c2mhNZiyYooBtT%2Fwhy%20did%20my%20import%20fail.png?alt=media&amp;token=e761734f-b099-4c67-bb99-d4cfb441fdee" alt=""><figcaption></figcaption></figure>

The messages under “**`ICSRs not imported`**” explain the specific error. If you do not understand a particular error message, please [contact UMC](mailto:support@who-umc.org) for assistance.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.who-umc.org/vigiflow/import-data/how-to-tell-why-an-import-has-failed.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.