Decide a suspended cleanup
A route with the delete behaviour Deactivate in the target system reports every record that no longer belongs to its scope as a deletion after a full run. When that suddenly concerns a conspicuously large share of the data set, Xchange does not carry the cleanup out but suspends it and asks you. This guide shows what to base the answer on.
The running example is the route Preislisten-Export Webshop with the notice "Cleanup suspended — 412 of 1,038 transmitted records no longer match the data filter."
What you need
- The Operations — Execution permission at the Full level. With Read you see the notice but not the link inside it.
- A way to look into the target system. Without it you cannot place the two numbers.
The halt costs nothing: the route's automation stays switched on, and everything except the cleanup keeps running. So you can take your time.
Find the notice
The item sits in orange in Action required; the row leads to the route's detail under Execution. There the notice sits at the top of Operational information, with both numbers and the Decide action.
Check the two numbers
Before you open the dialog, answer a single question: did those 412 records actually drop out of scope — or does it only look that way?
Three causes come into question, and two of them are a false alarm:
| Cause | How you recognise it |
|---|---|
| The data set really changed. | There was an occasion — a price list was retired, an item group discontinued. The number fits that occasion. |
| The data filter was changed. | The route was edited shortly before and a configuration snapshot activated. The comparison of the last two states shows it line by line. |
| The source system answered incompletely. | There was no occasion, and in the History the run comes out markedly smaller than on the days before. |
If the route is cleaning up for the first time, a large number is normal and no cause for alarm: the first cleanup catches up on everything that has dropped out of scope since the transfer began.
Decide
Click Decide in the notice. The dialog restates both numbers and offers two answers:
Release transmits the reports after all. Each of the 412 records goes to the target system as a deletion — what the target system makes of that is its own decision. Choose this when the number fits a real occasion.
Discard records that the cleanup is not carried out this time. Nothing goes to the target system, the notice disappears. Choose this on any doubt — see below for why that is the cheaper direction.
Cancel leaves the notice standing. The item stays in Action required until you take one of the two routes.
Discarding costs nothing. A suspended run is never replayed but always recalculated: the next full run with a cleanup determines the records anew. If the data filter was the cause and you set it back, the notice disappears by itself, without your having to decide again.
Xchange does not take a release back. The reports are out. Those records are transmitted again only once they match the data filter and a run picks them up — whether and how the target system lifts the deletion mark in the meantime is up to it.
So on doubt, discard and look for the cause. The cleanup comes back on its own with the next run.
What comes next
After Discard, the route carries the grey status Cleanup declined under Execution as its last run — so the information that nothing went out this time stays on record.
If the data filter was the cause, correct it in the route's draft and activate it. If it was the source system, start a full run with a cleanup once it is repaired and look at the numbers again.