History
History is the list of all jobs — every single record Xchange has processed, with its result and its path. On the left are the jobs, filtered by period, route, connection, status or run; on the right, for a selected job, you see what happened to it, which steps it went through and which message went over the wire along the way.
The proof is here. Execution tells you whether a run went through cleanly and counts its jobs; the individual job is shown by History. When someone asks whether delivery 80234 really arrived at the logistics partner and what exactly was sent, the answer is here. What a job is and how it relates to a run is explained by the concept Execution.
What is here is subject to the retention period. Jobs are cleaned up after their period; if you need proof beyond the period, save it outside Xchange beforehand.
Permissions
The screen follows the History permission:
| Level on History | What you can do here |
|---|---|
| None | nothing — the History menu item is missing |
| Read only | search and open all jobs and read them down to the sent message; Cancel and Reprocess are missing |
| Full | additionally cancel a running job and reprocess a failed one |
The filter bar is fully available on both levels — a filter only narrows down what the list shows. Two ways lead out of this page and follow the permission of the destination: Go to route opens the route's configuration, Open clarification opens Clarification.

Layout
| Area | What it shows |
|---|---|
| Filter bar (top) | seven filters that decide which jobs the list contains at all |
| Job list (left) | one row per job, newest first |
| Job details (right) | the selected job in sections — from the key data to the sent message |
The filter bar
Seven filters, in this order:
| Filter | What it narrows down by |
|---|---|
| Period | when the job last did something — the options are Last X Hours, Today, Yesterday, Last X Days, This Week, Last Week and From / To for a period set by hand; for the two X options you enter the number yourself |
| Quick search | record (key or display value), correlation ID, message ID or external key |
| Status | individual statuses or a whole status group, several at the same time |
| Step status | jobs in which at least one step shows Already present, Skipped (condition), Skipped (not present), Skipped (no change), Skipped (echo detected) or Skipped (no elements), several at the same time |
| Connection | all jobs of the routes of one connection |
| Route | one route; routes with the same name are told apart by the connection in the second column of the selection |
| Run reference | all jobs of a single run |
With Last X Days, today counts as the first day. Last 3 Days on September 25, 2026 covers September 23 to 25, and the field shows the dates for it: Last 3 Days (Sep 23, 2026 — Sep 25, 2026). The smallest number is 2; for a single day there is Today.
The period is set to the last 24 hours by default. The quick search searches the jobs for a piece of text anywhere within the value; the period limits this search.
The Run reference lifts the period. If you enter one, Xchange clears the period so that the whole run appears, even if it is older; the run reference itself is then the limit. If you clear the field again, the period you had before comes back. This is how the way from Execution leads here: a click on a row under Recent runs opens this page with the run reference in the filter, and so does Show in History on a run that is running right now.
In the status filter, the group row is itself a filter. The selection list holds three groups — Active, Action required, Completed — and below each, indented, its statuses. A check mark on the group sets all check marks below it, and the check mark on the group disappears as soon as you deselect one of them again. So you can filter roughly by "everything that is still open" just as well as by a single one of the 22 statuses.
The Step status asks about individual steps, not about the job. A job appears as soon as one of its steps shows the selected status — even if the job itself is Succeeded. To find the jobs that succeeded but in which a follow-up step did not find its record, select Skipped (not present) and, under Status, the value Succeeded. What counts is the status the step table of the job details shows for the step.
A button in the bar resets all seven filters to their initial state — the period is then set to the last 24 hours again.
The filters are in the address
The filters you set are in the page address. A reload restores the same selection, and a bookmark or a link you pass on opens the list filtered exactly as you saved it — if a job is open at the time, the link opens it too. If you change a filter, the open job stays in place.
The job list
Eight columns, in this order:
| Column | Content |
|---|---|
| Last activity | when something last changed on the job — the column the list is sorted by |
| Triggered | when the job was created |
| Record | the record the job is about — with its display value, e.g. the document number 1001, and in grey below it its key, e.g. Key 1944 |
| Route | the route that processed it |
| Direction | Import, Export or Internal, as a tag with an arrow |
| Connection | the connection of this route; empty for an internal route |
| Status | the result, with color and symbol |
| Duration | how long it took |
Next to open details, only Last activity and Record remain as columns; the other six details move into the line below, each with its label.
The two time columns show the distance to now — "20 minutes ago". The exact point in time is given in the tooltip: Triggered: Oct 8, 2026, 8:52 AM.
The Record is bold. If a job relates to the whole scope of a route — for example with a route-wide cleanup —, a dash appears in this place.
The display value is the value you know the record by; the key is the one Xchange recognizes it by. For a document from SAP Business One, that is the document number next to the internal key. Where the display value comes from is set by the route's Display field. If a job has none — because its record has not been read yet or the route has no display field —, the key stands alone. Otherwise it stands beneath the display value, even when the two are equal.
For a job with several attempts, the Duration column states both — the duration and the number of attempts. A job that is running right now shows running … instead of a duration.
The statuses
The Status column knows 22 values. They are grouped here as in the status filter:
| Group | Status | Meaning |
|---|---|---|
| Active | Queued | The job is waiting until it is its turn. |
| Running | It is being processed right now. | |
| Retry pending | An attempt failed, and the next one is scheduled — when is shown under Next retry. | |
| Cancellation requested | Someone chose Cancel; the job ends at the earliest possible point. | |
| Action required | Clarification | It failed permanently and is waiting in Clarification. |
| Skipped (clarification open) | It was left aside because the same record is already waiting in clarification. | |
| Manual review | It is waiting for a decision. | |
| Completed | Succeeded | It went through. |
| Clarification resolved, Clarification closed, Clarification superseded | Its clarification case has ended, and the second word says how — as described by the status in Clarification. | |
| Review resolved, Review closed, Review superseded | The same for a review. | |
| Skipped (condition), (deleted), (echo detected), (never transferred), (no change), (not present), (stale) | It did not need to be transferred. The addition says why; the reasons are explained in the concept Execution. | |
| Cancelled | It was cancelled. |
An ended clarification case changes the row. As long as the case is open, the row shows Clarification; once it has been decided, it shows e.g. Clarification resolved, and the row is no longer colored as an error.
The list loads more in blocks of 50 rows as soon as you scroll to the end. Above 200 loaded rows it stops refreshing itself, and says so. Applying the filter again fetches the current state.
Above the list stands how many jobs the filters match, e.g. 12,403 operations — every match, not only the loaded rows. It counts jobs, not documents: a record processed three times counts three times. While a run is working, Xchange recounts at most every two seconds; once the list has stopped refreshing itself, the number stays put as well. If the filter matches no job, the count is not shown.
The job details
The header carries route and record — Lieferaufträge Kessler · 80234 — and next to it the status as a tag, below that direction, route type and connection: Export · Processing · Kessler Logistik. An internal route has no connection; there it reads just Internal · Processing. On the right is Go to route. The sections follow below in the order this page describes them; each appears only when it has something to say for this job.
General information
The key data of the job:
| Detail | Meaning |
|---|---|
| Trigger | what triggered it — e.g. Event or Schedule; for a job started by hand, with the user, e.g. Manual · initiated by MBRANDT, for a released cleanup released by |
| Reason | only for a deletion: why the job ran as one — Deletion — deletion marker in the source or Deletion — no longer delivered |
| Configuration version | the snapshot it was processed with, e.g. v7 |
| Run | the run it belongs to, with point in time and run type. If the run read incrementally, the information icon beside it opens Read position at start and Read position at end: the position it read from and the one it left for the next run — both unchanged, exactly as Xchange stores them: the values read per field of the change filter, or the connection's change token |
| Cleanup for run | for a cleanup, the run it cleans up after |
| Message ID | only for a route with a Message ID set: the identifier of the incoming message; if the message lacked it, a dash appears there |
| Correlation ID | the identifier under which this one job appears in the logs |
| Repeat of / Dispatched from / Redelivery of | where this job comes from, if it was not the first |
| Repeats / Redeliveries | what has come out of it |
The references in this section are links. Run and Cleanup for run filter the list to that run; Repeat of, Dispatched from, Redelivery of, Repeats and Redeliveries open the job in question.
If the configuration has changed since this job, Xchange states below the Configuration version which snapshot is active today. A job is always processed with the snapshot that was active when it was created — that is why an old error can be explained even if the route looks different by now.
A repeat and a redelivery are two different things. A repeat is Xchange's own second attempt; a redelivery is the external system delivering the same message once more.
Records
The record on both sides: Internal 80234, External KS-778341 — each with its display
value and, in grey below it, the key where the two differ. Here you see which document on the other side belongs to which one here. The far side
is the record that this job's primary step addressed in the target system; that is why the name of
this step appears next to the heading. If the primary step did
not succeed, its outcome follows the key, e.g. "not found" when the record was missing in the
target system. If the job addressed no record on the other side, this line is omitted. If the link
is missing altogether, the section says so explicitly. For an internal route both records are in
SAP Business One; there the lines are called Source and Target.
Status and history
Current status, Attempts and — if the job failed — Error and Next
retry. The times appear below: Total, Processing, Waiting and Avg / attempt.
For the proof case 80234 these are 3 s total, 3 s processing and < 1 s waiting — the
waiting time is what the job spent in the queue before it was its turn. As long as the job has
not finished, Total and Waiting are missing.
If the job is in Clarification or is waiting for a decision, this section holds the way there — Open clarification or Open review. With Skipped (clarification open) it is called Open blocking clarification: it does not lead to a case of this job, but to the case of the same record that it is stuck behind. A job that held fields in a conflict is waiting for a decision and carries Open review — see Conflicts.
Execution steps
One row per step of the route, in its order and as it stood at the job's configuration version, with the columns Step, Status, Action, Error, Attempts, Last change and Messages. The step is named as in the route, in the proof case Lieferauftrag; if a route has several steps, the primary step carries the addition (primary step).
A step that works per element of a list has an indented row per element below it, e.g. Element ARM-4711. If you come to an element from Clarification, its row is highlighted.
If a step failed, it appears as Failed with its error. If the job did not reach it, it appears as Not run, or as Pending while the job is still running; Attempts and Last change then show "—". If no step ran, the section reads No step was executed. — for a skipped job this is normal.
Action states what the target system confirmed for this step: Created, Updated, Deleted or Executed. In the proof case it reads Created — Kessler created the shipment order. For a step with the write intent Create or update you see here which of the two happened. Updated (create refused) means the target system refused the create and Xchange updated the record a second lookup then found instead; Error shows the refusal. Where the step failed or wrote nothing, the cell shows "—". If no step of the job carries an action, the column is left out; the same goes for Error when no step has an error.
The number under Attempts means the same as the one under Status and history: how many attempts there actually were — here relating to this one step. If a job is waiting for its retry, both places count only the attempts that have already taken place.
Under Error the target system's message appears verbatim. Four messages are worded by Xchange itself:
| Message | What it means |
|---|---|
| The operation ended while this step was running. Whether its request reached the target system is not recorded — check there before running it again. | The job was ended in the middle of this step. Whether anything was written in the target system is open. |
| The operation ended before this step sent its request. Nothing was written to the target system. | The job was ended before this step sent anything. |
| The record was written but could not be read afterwards. The next attempt reads it again without writing it a second time. | After the write, Xchange reads the record so that following steps can work with it. This read failed; the job is retried, and the step does not write again. |
| The target system does not allow reading the written record. Later steps receive the answer of the write call. | The target system offers no read for this address. The job continues, and following steps work with what the target system answered to the write. |
With the first two, Xchange appends the reason the job ended — Reason: ….
In the Messages column, Show opens a dialog with the sent message and the response of this one step. If a step has neither, the cell stays empty. The column is missing when no step has a message or the only step shows its messages further down anyway.
Conflicts
Only for a route that has set Keep value in … or Submit for review for a field — the rules are under Routes — Behavior. The section has one row per such field on which one of these rules decided in this job. Fields that follow the source anyway, and fields where there was nothing to decide, are not listed; if there was nothing to decide in a job, the section is left out. Which system is the source and which the target follows from the connection and the direction in the job's header; for an internal route both are SAP Business One.
| Result | What happened to the field |
|---|---|
| Value taken from … | Only the source changed since the last synchronization; its value replaced the one in the target system. |
| Value kept in … | The value in the target system stayed: in a conflict the rule Keep value in … applied, the source delivered no value at the first synchronization, or the target system was chosen in Clarification. |
| Submitted for review | The two sides held different values, and Submit for review applies to the field. It was not written but submitted to Clarification. |
| Removed | Only for a row of a list that the target system replaces as a whole: the list sent did not contain the row, and the target system removed it. |
In place of the ellipsis, the result names the system — the connection, or SAP Business One. Previous value shows what was in the target system before the job, Delivered value the source's value; for Removed both show "—". How Xchange recognizes the state of a field is explained under How Xchange recognizes a conflict.
Fields of a list are listed per row, the row named by its key: "DocumentLines — ARM-4711 — Quantity". A row without a field — "DocumentLines — ARM-4711" — is the row itself, for example one deleted in the target system. A list that Xchange compares as a whole has one row with the appendix "(compared as a whole)". Which list is compared how is under Lists.
A conflict holds only its own fields. Xchange writes all other fields; the job ends with Manual review, and under Status and history Open review leads to the case.

In the example: order WS-2026-104864 of the route "Bestellungen Webshop", processed on
08.10.2026 at 09:05. The payment method changed on both sides since the last synchronization, and
PaymentMethod is set to Submit for review. Xchange updated the document without this field.
Attempt history
Only from the second finished attempt on: one row per attempt with No., Started, Outcome and Message. The outcome is the status the attempt ended with, with two values of its own:
| Outcome | What it means |
|---|---|
| Interrupted | The attempt was cut off before it finished, and the job was queued again. |
| Outcome unknown | Whether the write reached the target system could not be determined. |
Message names the step at which the attempt failed, and its error: Step "Bestellung anlegen": ….
Dispatched to
Only for a job of a dispatch route, and then in place of the execution steps: the target routes it was passed on to, with the job that was created from it there. If nothing was created, the section distinguishes three cases — not yet dispatched, no rule matched, or the job went to manual review.
Received message
For incoming jobs, the content as it arrived. The section belongs to incoming jobs: for the proof case 80234, an export, the execution steps are followed directly by the sent message.
The header of the section has Download; it delivers the complete message as a file. Below it, a preview shows the content with line numbers, a JSON message indented. After 30 lines the preview scrolls.
Sent message and response
What Xchange sent to the target system and what came back, each with method, target, point in time, content and the status code of the response — in the proof case Status 201. These two sections prove what was sent to which address when and what came back.
If the target system does not return the record with the write, Xchange reads it afterwards, and that record appears below the status code — which is why a complete record can appear under Status 204.
For an outgoing route, the two sections for the primary step appear right here, collapsible; for an incoming route you reach them through Show in the step row.
If the step needed several attempts, the sections show the last one and say so: Showing the last of 3 attempts. One exception: if the last attempt only established that the document already exists in the target system (Already present), the sent message comes from the earlier attempt that wrote it — then it reads The sent message is from an earlier attempt. The last attempt only checked whether the record already exists in the target system.
If the record went out in a batch call, a line below method and target names the call that carried it and which part of it the record was, such as Sent in a batch call (POST $batch), part 3 of 20 — if the target system does not name the call, just Sent in a batch call, part 3 of 20. Method and target above show the entry as it would have read as a call of its own. An error still concerns this record alone — every entry of a batch call has its own result. If the record went out in a call of its own, the line is left out — as the only job of a batch call it is still there, as part 1 of 1.
Two empty cases: The step sent no message body. means there was nothing to send; No sent message is available for this step. means the record is missing. The same on the response side — with a status code, the target system answered and just sent nothing along; without a status code, there is no response at all.
When the message is large
The preview of the received message reaches up to 1 MB. If the message is larger, it shows the beginning, and below it says: Showing the beginning of the message. Use "Download" to get the complete message (3.4 MB). A JSON message ends at a line boundary. You get the complete message through Download, however large it is.
There are two messages about this:
| Message | What it means |
|---|---|
| The preview could not be loaded. Use "Download" to get the message. | The preview is missing; the content can still be reached through Download. |
| The message could not be downloaded. Try again. | The download failed; the message itself still exists. |
Sent message and response are always readable, however large the received one was.
Intervening
Two actions, both only with the History permission at Full and both only with a matching status:
| Action | When it appears | What it does |
|---|---|---|
| Cancel | as long as the job is still pending, running or waiting for its retry | ends it at the earliest possible point |
| Reprocess | for a job in clarification, in review or cancelled | processes it once more with the active configuration snapshot |
Both ask for confirmation first. Reprocess takes the snapshot active today, not the one under which the job originally ran — so a cause you have fixed in the configuration in the meantime takes effect.
The third button, Go to route, leads into the configuration of the route that created this job. If the route has since been removed from the active snapshot, Xchange reports that.
A failed job, read
Order WS-2026-104861 appears in the list with the status Clarification. Under Status and
history the error Required field 'CardCode' has no value. appears, with Open clarification in
the header of the section; in the execution steps "Bestellung anlegen" is Failed. The Received
message shows why: the order lacks customer_no, from which CardCode gets its value. There is
no sent message — the step failed before anything went out.

The case is decided in Clarification.
See also
- Decide which side wins in a field conflict (guide) — set the rules and decide submitted fields
- Execution (reference) — operation per route, from which you come here
- Clarification (reference) — deciding and resolving failed jobs
- Routes (reference) — the configuration that Go to route leads to
- Routes — Behavior (reference) — the rules that decide the conflicts
- Execution (core concept) — run versus job, retry, outcome of a run