Run on a schedule
In this guide, "Artikel Cambira Austria" gets two schedules: at night at 02:00, the
changed items go to the Austrian company, and on Sundays at 03:00, the whole selection.
The two schedules answer two different questions. What has changed? — that is the question of the daily run. What has disappeared? — only a full run asks that, and only on a full run can Cleanup be switched on. A route that asks only the first question transfers cleanly for years and meanwhile overlooks every old record that stays behind in the target system.
Here, the clock sets the pace. If the route is instead to react to an event in SAP Business One — every time a document changes —, the way is described in React to a change in SAP.
What you need
- Three permissions, each at the Full level: Routes creates the schedules, Activation activates the snapshot, Automation releases the route at the end — see Permissions.
- A route that reads data on its own. On a route with the data origin Dispatch input, validation flags a schedule with "A route with a dispatch-inbound trigger must not have a timer or event trigger". It runs when the dispatching route gives it something.
- The Automation tab of the opened route. There, the triggers are listed on the left, and their settings on the right.
Xchange saves every entry automatically. In operation, it takes effect only with the activated configuration snapshot.
1. Create the daily schedule
- On the route's Automation tab, choose Add trigger at the top right. The Choose trigger type dialog opens.
- Choose Scheduled — "Starts the route on a fixed schedule." — and confirm with Select.
- The form appears on the right. Set Frequency to Daily, Time to
02:00. - Set Run type to Incremental.

In the list on the left, the trigger now appears as Scheduled, with "Daily 02:00 · Incremental" below it. That is the line by which you tell two schedules apart later.
About the frequency. The options are Every N minutes, Every N hours, Daily, Weekly and Monthly. The first two ask for an Interval instead of a time. Weekly requires at least one day under Weekdays — until then, the field stays marked as required. Monthly asks for the Day of month and points out for 29, 30 and 31: "Months without this day are skipped — choose "Last day" for the end of the month."
For rhythms beyond this form, Mode offers the Advanced setting with a Cron expression. The fields are described in detail in Routes — Automation.
2. Check when it really runs
Above the Run type, Next runs shows the next three times that result from your entry — in the image above Oct 9, Oct 10 and Oct 11, 2026, each at 2:00 AM. Read the line before you move on — a mistyped weekday stands out here, and otherwise only in operation.
If you point the mouse at the label, "Times in server time" appears. So the times are those of the server. If the server and your workstation are in different time zones, the line shows the difference.
3. Add the second schedule alongside
The Sunday run is created the same way, with different values:
- Again Add trigger, again Scheduled.
- Frequency Weekly, under Weekdays Su, Time
03:00. - Run type Full.
The list on the left now has two entries. Both belong to the same route, and both apply side by side — they run at different times with different run types.
What Xchange flags is exclusively the other case: the same run type twice on one route. Validation then reports "Run type" is already in use.
4. Attach the cleanup to the Sunday run
On the full run, under Cleanup, there is the checkbox Report records no longer delivered. Check it on the Sunday run; the checkbox belongs to the full run alone.
What it does is shown by a case from this route: ERS-2087, "Dichtungssatz Nordfluss", was in
the item group 101 Ersatzteile and was moved to the item group 104 Auslaufartikel. This takes the item out of
the route's data filter — the Sunday run reported it to CAMBIRA_AT, and because the
route's delete behavior is Deactivate in the target system, it is inactive there instead of still
active. Without the cleanup, it would simply have stayed behind in the Austrian company.
Reporting is a separate run: in the run list, it appears as Cleanup below the run it came from.
You decide whether such departures are reported. Which records these are in detail, Xchange determines itself.
Cleanup appears only when two things come together: the run type is Full, and on the Behavior tab, the Strategy of the delete behavior is set to Deactivate in the target system. If it is set to Do nothing, reporting is dropped — and the checkbox with it. The way to this setting is described in Routes — Behavior.
5. Release — only then does the route start
A route starts only when the release is added to the trigger. As long as the switch in the Automation column on the Execution screen is off, the schedule rests. You can still start the route by hand at any time.
- Validate and activate the draft — the way is described in Validate and activate.
- Switch to Execution and flip the switch in the Automation column of this route.
From now on, the two schedules start the runs. Whether the first of them ran cleanly, you see the next morning — Check whether a run went through cleanly.
Where the choice looks different
Which values the Run type offers depends on the route's Data origin — the field on the General tab that is set when the route is created and is fixed afterwards:
- Dataset — the route of this guide: Full and Incremental.
- Queue — only Drain queue. In return, the Items per cycle field appears there, which may stay empty — then the run fetches whatever is there.
And a warning you may come across when you set a full run to a short interval: "A full run transfers all data every time. At such short intervals that is usually unnecessary — "Incremental" transfers only changes." You can ignore the warning.
What comes next
Whether the first scheduled run went through cleanly is shown in Check whether a run went through cleanly.
See also
- Transfer only changes (guide) — how an existing schedule is switched from Full to Incremental
- Choose the right trigger (guide) — clock, event or by hand
- Release or discard a suspended cleanup (guide) — when a run finds an unusual number of departures and Xchange asks before reporting
- Routes — Automation (reference) — every field of the tab in detail
- Triggering (core concept) — run types, triggers and how they work together