Inspecting run items
A run item is the per-resource breakdown. One run with three enabled resources has three run items. Each item carries everything you need to understand what happened to that resource in that run.
What you see on a run item
| Field | Meaning |
|---|---|
| Phase | Where the run is right now for this resource, or done. |
| Result | Succeeded, Failed, or in progress if still running. |
| Counts | Per-step totals: extracted, transformed, loaded, skipped, errored. |
| Started / finished | Wall-clock time and duration. |
| Errors | A list of per-row errors with the source ID, the phase that broke, and the error text. |
| Mapping version | The version pinned at the start of this run for this resource. |
Reading errors
Errors are per-row, not per-run. A typical failed run item shows something like:
errored: 12 of 4,317Click through to see the twelve specific source IDs, the phase each broke in, and the error message Shopify (or JSONata, or the source API) returned. From there you can:
- Click the source ID to see the original source row.
- Click the staged record to see the payload that was rejected.
- Open the mapping at the version pinned to this run and trace why the output was wrong.
Counts that don’t add up
A few things to know:
- Transformed ≤ extracted — some rows may produce no output if the mapping returns nothing for them.
- Loaded + skipped + errored ≤ transformed — only-dirty narrows what load looks at.
- Skipped includes both conflict-strategy skips and only-dirty skips. The breakdown view splits the two reasons apart.
Long-running items
The run item shows live progress while the work is happening: pages of source pulled (extract), rows transformed (transform), batches loaded (load). Useful to estimate time-to-finish on large catalogs.
Last updated on