How to read a run
What a run's numbers and statuses mean, and where to find what failed.
Every run appears on the “Sync” page (the last one of each module) and under “History” (all of them).
Status
| Status | What it means |
|---|---|
| Completed | Everything that was read was written or was already right. |
| With errors | The run finished, but some records need attention. The others were written normally. |
| Failed | The run could not happen at all, for example because the ERP was not answering. |
A record with a problem is skipped and the run goes on. One bad item does not stop the rest.
Numbers
| Counter | What it counts |
|---|---|
| read | Rows that came from the ERP. |
| created | New records in the shop. |
| updated | Records that changed. |
| unchanged | They were already the same and were not written again. |
| drafted | Products retired because they are missing from the ERP. |
| deleted | Only if you turned permanent deletion on. |
| failed | Records with an error. |
| not in shop | Items or customers that are not in the shop and were not created. |
Run details
Under “Run details” you see how it started (scheduled or by hand), whether it read changes only or everything, and the list of records with an error, grouped by cause.
Every error has:
- What happened: one sentence in plain language.
- What to do: up to two buttons that fix the cause, and “Try again”.
- A link to the code’s article, in the Errors section.
Some errors are temporary and the service retries them by itself: when the ERP or the shop does not answer, when the session expires, or when time runs out.