Monitoring & debugging
Every byte of data Graftport touches is inspectable from the UI. There is no separate logging tool — you don’t need it.
Where to look
| If you want to know… | Look at |
|---|---|
| What this run did, end-to-end | The run detail page (/runs/<id>). |
| Why one resource failed | The Errors tab on that page. |
| Whether Shopify holds what we prepared, record by record | Data explorer — Data in the sidebar. |
| What we pulled from the source | Extracted data. |
| What payload we sent (or would send) to Shopify | Staged records. |
| Which mapping version produced this payload | The run’s Configuration tab. |
Two screens cover almost everything. The run detail page answers “what happened during this run?” The Data explorer answers “what does this record look like now?” — across every run, one record at a time.
The pages:
- Data explorer — the record browser: source beside mapped output, with a Match / Drifted / Failed / Pending verdict on every row.
- Inspecting run items — the per-resource view with counts, errors, and timing.
- Extracted data — what Graftport pulled and how to read it.
- Staged records — payloads ready to push, with their pending and loaded state.
Last updated on