Chapter 8
8. History and results
Open History to inspect imports. Each job shows its filename, status, recorded rows, outcomes, start time, and duration.
8.1 Find a job
Open Filters to filter by filename or status and select a sort order. Select Apply filters. Use Clear to remove filters.
After you apply a filter, the filter control reads Filters active.
Select a filename to open the job. Use Previous 50 and Next 50 when results span several pages.
| Job status | Meaning |
|---|---|
running |
The import is still processing |
cancelling |
Cancellation was requested; unfinished work is stopping |
completed |
The job reached its end; inspect row counts for failures |
failed |
The job recorded a failure; inspect the message and row evidence |
cancelled |
A cancellation stopped unfinished work |
interrupted |
The application stopped before recording a final result |
The final job status does not replace row inspection. A failed or stopped job can contain completed changes.
8.2 Inspect a row
Job detail shows row outcomes, search values, match counts, and actions. Select Details to expand a row, then Hide details to close it.
ID means identifier.
| Evidence | What it tells you |
|---|---|
| Matched asset IDs | Assets returned by the search |
| Intended target IDs | Assets selected by the match policy |
| Attempted target IDs | Assets Data Wrangler tried to change |
| Succeeded target IDs | Assets with a recorded successful operation |
| Failed target IDs | Assets with a recorded failed operation |
| Planned fields | Values prepared for writing |
| Confirmed fields | Values recorded after a successful write |
A matched asset is not automatically a changed asset. Planned fields are not proof of a completed write.
Use Show failed rows to focus on failures. Show all rows returns to the complete result list.
8.3 Understand partial changes
Update every match processes assets separately. If a later update fails, earlier updates remain.
Creation also has two steps: create the asset, then apply the write fields. If the second step fails, the asset can exist without all intended metadata.
A failed row can therefore contain a successful operation. Check target identifiers, messages, and the asset in CatDV before repeating it.
8.4 Recover from stopped or failed work
- Read the job message and the last recorded rows.
- Confirm uncertain or partial results in CatDV.
- Correct the connection, mapping, policy, or source data that caused the problem.
- Prepare a file containing the rows that still need work, with its header row.
- Stage that file and inspect the saved setup before running.
There is no automatic resume from the last row. Running the original file again starts a new job and can repeat completed writes or create more assets.
Previous: Running an import · Contents · Next: Licensing and updates