> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/system-admins/administration/data-manager/troubleshooting/data-not-imported.md).

# Data Not Imported

Investigate a missing, pending, or failed Data Manager import.

Start in Job Manager with the exact file or log identifier.

## Check the submitted file

1. Open `MDM` > `File history`.
2. Search for the file, configuration, or log identifier.
3. Open the file.
4. Review its status and timeline.
5. Compare `Original` with `Errors`.

If the file does not appear, confirm that the source system submitted it to the expected configuration.

## Check queued processing

Queued files depend on the bulk-file processing service job.

1. Open `Catalog` in Job Manager.
2. Search for the bulk imported file processing job used by the instance.
3. Confirm its pause state and schedule.
4. Open `Run history`.
5. Review the latest run, parameters, and linked data logs.

See [Troubleshoot file imports](/documents/system-admins/administration/job-manager/troubleshooting/file-imports.md).

## Check the file format

Download the original file from File Details and compare it with the format required by the configuration.

When middleware transforms the file, review the transformation flow with the integration owner. Do not change the Data Manager service to compensate for an unconfirmed source-format problem.

## Check empty input

An import can finish without creating records when the submitted file contains no data rows.

1. Open the file detail.
2. Review `Original`.
3. Confirm that data rows exist after the header.
4. Check the source export when the file is empty.

Submit a corrected file only after the source produces the expected records.


---

# 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://docs.hotwax.co/documents/system-admins/administration/data-manager/troubleshooting/data-not-imported.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.