Skip to main content
Use the Schedules tab in a context’s setup page to automate reconciliation execution. Each matching schedule defines when the Matcher engine automatically runs matching for the selected context.
Matching schedules set when automated matching runs for the reconciliation context. They do not pull any data. To schedule when a source ingests data, open a source and manage its ingestion schedules.

​
Accessing schedules

  1. Navigate to Configure → Contexts in the left sidebar.
  2. Click a context to open its setup page.
  3. Select the Schedules tab.
The Schedules tab applies to an existing context. For new contexts, save the context first.

​
Schedule list

The list shows every matching schedule configured for the context. Each row displays:
  • The cron expression
  • An Enabled or Disabled badge
  • Last run · Next run timestamps in UTC. The UI shows – for Last run until a schedule has run, and for Next run on a disabled schedule
  • Inline edit (pencil) and delete (trash) buttons

​
Creating a schedule

1
In the Schedules tab, click the Add matching schedule button.
2
A dialog titled Add matching schedule opens. Enter the schedule in the Cron expression field (placeholder 0 2 * * *, up to 100 characters).As you type, a live preview appears below the field. For common shapes, the preview shows a human-readable phrase such as “Runs: Every day at 02:00”. For valid but uncommon shapes, it shows “Valid schedule expression.” For a malformed expression, it shows an error. The preview is a hint and does not prevent submission.The preview recognizes interval and named-macro syntax such as @every 15m even though Matcher matching schedules do not accept it. The server accepts only a standard five-field cron expression and applies its cadence policy when you save.
3
The Enabled checkbox is on by default. Leave it selected to create an active schedule, or clear it to create a disabled one. A disabled schedule remains configured and has no next-run time. Later worker polls do not select it.
4
Click Create matching schedule.
Matcher evaluates a cron expression in UTC. It uses five space-separated fields: minute hour day-of-month month day-of-week.Common special characters:
  • *: any value
  • ,: list of values (e.g., 1,15,30)
  • -: range (e.g., 9-17)
  • /: step (e.g., */15 for every 15 units)
Examples:
  • 0 6 * * *: every day at 06:00 UTC
  • */15 * * * *: every 15 minutes
  • 0 9 * * 1-5: at 09:00 UTC on weekdays
Matcher does not support @every … syntax or named macros. When you restrict both day-of-month and day-of-week (not bare *), Matcher uses standard cron OR semantics. A match in either field triggers the schedule. The server requires at least five minutes between firings. The smallest permitted cadence is */5 * * * *. For example, the server rejects * * * * * and */2 * * * *.To validate an expression, use crontab.guru to preview when it will run.

​
Editing a schedule

Click the pencil button on a schedule row. The Edit matching schedule dialog opens with the current cron expression and Enabled state pre-filled. Update the fields and click Save changes. For an enabled schedule, saving recalculates Next run from the current UTC time. Disabling it removes that timestamp.
The edit dialog shows only the cron expression and the Enabled checkbox. Last run and Next run timestamps appear on the list row.

​
Deleting a schedule

Click the trash button on a schedule row. A Delete matching schedule? confirmation dialog appears. Click Delete to remove the schedule permanently.
Deleting a schedule is irreversible. It stops future worker polls from selecting the schedule. It cannot cancel a matching run that a worker has already picked up.