Traces
The Traces area shows every single transfer: which record, over which channel, with which task, when, and with what result. You reach it through the Traces navigation entry.
Where a value in the shop differs from the one in TRADElube, the real work is narrowing down the cause: was the value delivered that way, processed that way, or handed over that way? This area answers that per record and field, and you can look it up yourself without asking us.
What a transfer is, why its state hangs on the individual record rather than on the execution, and which states TRADElube keeps is described under traces.
Overview / list
The list opens filtered: of the five state filters above it, only Failed is ticked when you arrive. So at first you see only what went wrong, and not the many thousand transfers that went through. Whoever wants the others ticks them on.
Four buttons sit above the list, and all four require a selected row. Show Details opens the Details dialog with the transferred state. Goto jumps to the record affected: the product, the order or whatever it was about. That record has to still exist. Delete removes the entry from the traces, and Restart picks the transfer of this record up again.
Restart is what you need once an error is fixed. It changes nothing about the data, it only lifts the note that this record has already been dealt with. On the next execution it is included again.
Delete removes the log entry, not the record. The product or order it was about stays untouched.
The Filter field below searches the task name from the Context column and the content of the Details column, and a partial match is enough. It disappears as soon as a condition is set through Filter By. That menu carries the four fields Object Info, Changes, Executed At and Changes At directly, without the groups in front of them: there is only one. How a condition you have set is edited and combined is described under products.
Each of the five state filters carries the color of its state, and the same color appears in the list's State column. In a long list you recognize the failure by that color before you read it. What the five states mean is described under traces.
As soon as you select a row, its error message appears above the list, with short message, plain text and note. So you do not have to open the dialog to see what went wrong.
The list shows five columns:
| Column | Content |
|---|---|
| State | The state of the transfer. On a failure this shows not the state but the short message, Doppelte Produktnummer (duplicate product number) for instance |
| Context | Channel and task it happened on |
| Details | The record affected, with number and, where delivered, designation |
| Executed At | When the transfer ran |
| Changes At | When the transferred data last changed |
Sorting is fixed to Executed At, descending, so the most recent transfer sits at the top.
The list sits in a box that can be scrolled sideways, and here that regularly pays off: the two time columns on the right are exactly what you need when narrowing something down.
Below the list sit the pager, the Items per Page choice with the values 25, 50, 100 and 200, and the total number of transfers matching the filters you have set.
When you open the traces from a task
A second row of five buttons then appears below the list, acting on the whole list instead of on one row. List Restart picks up all transfers in the displayed list again, List Freeze stops them so the next execution does not touch them, and List Delete removes the displayed entries from the traces. Restart All and Freeze All do the same, but regardless of the filter set.
The difference between List and All is exactly that filter, and it is the reason to look at the state filters before clicking: List Restart means what is on screen right now, Restart All means everything belonging to this task.
The Details dialog
The Show Details button opens the state TRADElube has kept for this transfer.
At the top sit Object Info, State, Executed At and Changes At, and on a failure below them the error message with short message, plain text and note. You copy the whole content to the clipboard with the button at the top right, which is the quickest way to describe a case to us.
Later and Prior page through the kept states of the same record. Where none exists in that direction, the button is grayed out. The Show Diff checkbox next to them highlights what changed against the previous state, additions in green and removals in red. It only appears where a previous state exists.
With Show Diff the dialog answers the question "what actually changed" in a second, instead of leaving you to put two states of the data side by side.
On a failure the lower part shows the technical trail, that is the text the connected system or TRADElube itself reported. It is not written for you and does not have to be understood. It is there so that you can copy it and send it to us, and with it a case is settled in minutes rather than days.
Where else the traces appear
You reach the same view in four further places, each time restricted to a section of it:
- On the record in the Channels section, through the Show Traces button: everything about exactly this product in exactly this channel.
- On the channel in its Traces section: everything that ran through this channel. That section opens with the Failed state filter set and carries the List Delete button below the list.
- On the task: everything that run touched, together with the second row of buttons described above.
- On the dashboard in the error log, which summarizes the failed transfers and links here from there.
It is deliberately the same view and not four similar ones. Whoever has read it once reads it everywhere.
Further reading
- Traces (concepts): why the state hangs on the record and which states are kept
- Understanding error messages: how a message is structured and what the common ones mean
- Traces (guides): the path from the deviation to the cause, worked through an example
- Channels and tasks (reference): where an execution is started and where the second row of buttons appears