> 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/job-manager/troubleshooting/file-imports.md).

# File imports

Investigate pending, failed, canceled, or partially processed files.

Open `MDM` > `File history` and find the exact file or log identifier.

## Choose the next check

Use the current status and record totals together. `Finished with errors` means processing finished with failed records; it still requires investigation.

```mermaid
flowchart TD
    accTitle: Decide how to investigate an imported file
    accDescr: Pending or running files need a queue and timeline check. Other files need a status and failed-record review before any corrected data is submitted, because records may already have applied.
    A[Find the exact file log] --> B{Pending or running?}
    B -->|Yes| C[Check queue and timeline<br/>Wait for the original submission]
    B -->|No| D[Review status and failed-record totals]
    D --> E[Compare available Errors with Original<br/>Check the import configuration]
    E --> F[Confirm which records already applied<br/>Check how the configuration handles replay]
    F --> G[Correct the confirmed problem<br/>Submit corrected data if needed]
```

## Investigate a pending file

1. Confirm the file status and submission time.
2. Review its priority and configuration.
3. Check whether earlier queued files are still processing.
4. Open the relevant file detail.
5. Review the processing timeline.

Do not upload the file again while the original submission remains pending.

Use the cancel action only when it appears for the pending record and you have confirmed that the file should not process.

## Investigate failed records

1. Open the file detail.
2. Select `Errors`.
3. Search for the affected record identifier.
4. Compare the error with the same row in `Original`.
5. Open the import configuration.
6. Correct the source data or confirmed configuration problem.
7. Confirm which records already applied and how the configuration handles repeated records.
8. Submit corrected data through `Manual uploads` when needed.

Cancellation or resubmission does not reverse records that were already processed.

The `Errors` tab appears only when failed records have an available error file. If the tab is missing, use the status, record totals, and linked job or backend logs to continue the investigation.

## Investigate a missing file

1. Confirm the active product store.
2. Clear File History filters.
3. Search by file name, configuration, and log identifier.
4. Confirm whether the submission succeeded.
5. Refresh file data from `Settings` > `Data Fetch Status`.

If the source system did not submit the file, investigate that integration before changing the import configuration.

## Check the queue poller

Queued imports depend on the configured bulk-file processing job.

1. Open `Catalog`.
2. Search for the bulk imported file processing job used by the instance.
3. Confirm its schedule and pause state.
4. Review recent runs and linked file logs.

See [Configure Data Manager](https://docs.hotwax.co/documents/system-admins/administration/data-manager.md) for backend queue and configuration concepts.


---

# 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/job-manager/troubleshooting/file-imports.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.
