Skip to main content

Release or discard a suspended cleanup

On the Overview, Action required shows a row: a route's cleanup is suspended and awaits release. Xchange intends to tell a target system that records no longer belong there — and waits with it until someone has agreed.

The case is "Artikel Cambira Austria", the route that transfers the item master from CAMBIRA_DE into the Austrian company CAMBIRA_AT. Its data filter lets two item groups through, 100 Armaturen and 101 Ersatzteile — 1,186 items together. On Sundays at 3:00 AM it runs in full, with Cleanup turned on: what the route transferred earlier and is missing in the full run, it reports to Austria, where it is set inactive.

On an ordinary Sunday, that is a few items. The case this page is about is the other one: someone has changed the data filter — the condition ItemsGroupCode equals 101 has dropped out — and on the next full run 512 of the 1,186 items leave the selection at one stroke, exactly the Ersatzteile.

What you need​

Permissions

To decide, you need Execution at the Full level — M. Brandt has it. With Read only you see the notice in full, but without Decide: A. Vogt reads the hold, Brandt resolves it. More on this under Permissions.

You should also know which data filter is on the route and whether it was changed recently. That is exactly what the decision is about.

You have time. A hold stays in place until someone decides.

1. The row on the Overview​

The row appears in Action required as a warning: the run completed cleanly and held back what it was meant to report to the target system. On the right of the row is the Execution jump; a click on the row leads there, to exactly this route. The row also states how long the question has been waiting — the duration appears after the first quarter of an hour.

The same row sits behind the warning icon in the header bar, on every screen — see Overview.

2. What was suspended — and why​

On Execution, in the route's Operational information area, a banner with a warning icon is at the top. It states two numbers: how many of the transferred records were no longer delivered, and how many the route has transferred in total. At the end of the sentence is the Decide link.

A banner reports that 512 of 1,186 records were no longer delivered, and offers Decide.

What is suspended is the reporting after the full synchronization. The cleanup is a run of its own that follows the full synchronization and transfers exactly the records that have left — how this fits together is described under Transfer deletions or deliberately leave records in place. It is this second run that waits. The items in the Austrian company stay unchanged as long as no one decides.

Why Xchange asks: after every full run with cleanup, it checks how large the exit is in proportion to the transferred stock. If the share is unusually high, it holds the messages back. The reason is the most expensive mistake at this point: a data filter accidentally set too narrow turns half the stock into an exit, and without the hold, half the item list would be inactive over there before anyone noticed.

Two things about this that matter day to day:

  • Routes with a larger transferred stock are checked. With small stocks every exit is a large share, and the share is of little use as a warning sign there.
  • The threshold belongs to the setup; the UI names it nowhere. Only the hold itself tells you that a share was high enough.

3. Before you decide: a look at the data filter​

The decision has exactly one preliminary question: Should these records have left the selection?

  1. Open the route on the Source data tab and read the Data filter.
  2. Compare it with what it was before. The comparison of two configuration snapshots shows whether and when something changed on the route — see Configuration Snapshots.
  3. Check the number against the total: for "Artikel Cambira Austria" the data filter covers 1,186 items. An exit count of this magnitude means that a whole item group has dropped out — which points to a change; day to day, it is a few items.

If the number fits a change that someone made deliberately, the exit is genuine. If it fits nothing, suspicion falls on the data filter rather than on the data.

4. Release or discard​

Click Decide in the banner. The Suspended cleanup dialog opens. It repeats the two numbers and then says what the answers do: "Releasing reports the change to the target system, discarding transmits nothing — the next full run asks again."

If the question has been discarded before, the dialog says so — how often, when last and by whom, as a paragraph of its own below the question. Then someone has already decided here, and the same question came back unchanged. This is the only place where you see that.

Below are three buttons — Release, Discard and Cancel.

The Suspended cleanup dialog with the two numbers and three equal-ranking buttons.

AnswerWhat happens
ReleaseXchange creates the cleanup as a run and transfers the exits. What the target system does with them, it sets up itself; for "Artikel Cambira Austria" the delete behavior is set to Deactivate in the target system, so the items are set inactive in CAMBIRA_AT.
DiscardXchange transfers nothing. The exits remain recorded as such in Xchange, and the next full run asks the same question again — unless the records have returned to the selection by then.
CancelThe hold stays in place. The same applies if you close the dialog with the cross or the Escape key.

Both answers stand side by side with equal rank: both have consequences, and the data filter shows you which one is meant. The input focus is on Cancel, so the Enter key leaves the hold in place.

Discard leaves the question open. It is the right answer to a wrong data filter: you discard, correct the filter, activate the configuration snapshot — and the next full synchronization finds the items back in the selection; the question settles itself.

How you can tell it works​

After either answer, the row disappears from Action required on the Overview, and the banner disappears from the route.

The question itself is not a run. The Sunday run stands in Recent runs as Full with the outcome Succeeded — it ran through cleanly, whatever you decide afterwards. What is added depends on the answer:

AnswerWhat is added to Recent runs
Releasea run of type Cleanup that transfers the exits, with its own outcome
Discardnothing, because nothing was transferred. The answer is recorded all the same: if the next full synchronization holds the cleanup again, the dialog says that it was discarded before.

Run type Cleanup means: a run that refers to another one. The detail view of such a run therefore carries the Cleanup for run entry and with it points to the full synchronization it belongs to. A repair run without this reference — e.g. one you start with Transfer individually — is called Targeted instead.

The Recent runs table shows only the five most recent runs of the route. If the hold was some time ago, you find the rows via the History.

Easily confused: the cleanup in the settings​

In the Settings, under Retention periods, there is also a cleanup. It clears old processing data in Xchange; target systems stay untouched. A route's cleanup is the opposite: it transfers something outward and leaves the data in Xchange. Despite the same name, they are two things — see Settings.

What comes next​

See also​