> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/run-the-platform/virtual-machines/view-import-jobs.md).

# Viewing Import Jobs

Instructions for viewing and monitoring VM import job status, child jobs, and imported VM listings in VergeOS.

## View All Import Jobs

1. Navigate to **Virtual Machines** > **List** from the top menu.
2. Select **Import Jobs** on the left menu.
3. A listing of all submitted import jobs is displayed; double-click a particular job in the list to access the import job's dashboard with detailed information, such as individual child import jobs, logs, etc.

## See a Listing of the VMs Imported via an Import Job

1. Navigate to **Virtual Machines** > **List** from the top menu.
2. Click **Import Jobs** on the left menu.
3. All import jobs appear in the listing; **Double-click the desired import job**.
4. Child import jobs are displayed on the import job dashboard that appears. The VM column will display the names of the imported VMs.

{% hint style="success" %}
**A *****--View More--***** link is available at the bottom of the *****Child Import Jobs***** section to view additional child jobs when all do not fit on a single page.**
{% endhint %}

{% hint style="info" %}
**A UUID (rather than the VM name) displayed in the VM field indicates that a VM with that unique identifier already existed in the VergeOS system (e.g. previously imported). If a UUID is displayed, the VM was imported as a** [**snapshot**](/automate-protect-and-extend/backup-and-dr/snapshots-overview.md) **to avoid inadvertently overwriting an existing VergeOS VM.**
{% endhint %}


---

# 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.verge.io/run-the-platform/virtual-machines/view-import-jobs.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.