Import History
Check whether a template import finished, and read the errors when it did not.
On this page
Every run of an import template is a background job, and Import History is where you check on it: whether it is still running, whether it finished, and exactly which rows failed when it did not.
Where to find it#
Configure Settings → Other → Import History. The page needs the Manage import history permission, which the default Owner and Admin roles hold; grant it to a custom role on its own if someone who runs imports should be able to check on them without the rest of Settings.
Reading the list#
Each row is one import job, newest first:
| Column | Shows |
|---|---|
| Import ID | The first eight characters of the job's id. Hover to see the full id; quote it to support if you need help with a run. |
| Dates | When the job was queued and when it last changed. |
| Status | Pending, Running, Finished or Failed. |
| Errors | For a failed run, the number of errors and each failing row's message. |
A completed import has created everything the preview promised; the new branch is in the Map at the workstream you imported into. A failed import names each row that could not be created and why — a name that resolved to nothing, a type the target cannot hold, a parent that is missing or archived, a date in the wrong shape. An import is all or nothing: DevStride checks every row before it writes anything, so a failed import has created nothing and left nothing half-built. Fix the workbook and import again; the page keeps every run, so you can compare attempts.
The page keeps the record of every import, but not always the file it read. If you try to run an older import again and its file has been removed, DevStride says so and asks you to upload the file again.