Skip to main content

Frequencies

In briefA frequency is a named pattern that decides which dates a job qualifies on: daily, weekly, monthly, quarterly or yearly, or one of the two special periods, On Request (never built, added by hand) and Annual Plan (the dates of a calendar, which can be the Master Holiday Calendar). Frequencies are shared by every workspace. The job's own timing, retries and reruns are set per frequency on the job, not on the frequency.

WhereDesign › Toolkit › the Frequencies tab. New Frequency opens the New Frequency dialog, with Name, Description and Recurrence Pattern on the left and the forecast on the right; a row's menu has Edit (or View), Cross Reference and Delete. A job is given its frequencies on the Frequencies tab of the job editor.

When

  • You need a job to run on a repeating pattern, such as every weekday, the 1st and 15th, the second Tuesday, the last working day of the month, or the last working day of the quarter.
  • You need a job that runs only when an operator adds it, or only on a fixed list of dates.
  • You want to see which dates a pattern produces while you edit it.

To check what a workflow will actually build on a date, with its working days and calendars applied, use the workflow editor's Forecast view instead.

How

  1. Open the Frequencies tab of the Toolkit and select New Frequency.
  2. Name it, choose the time period and the pattern, and check the highlighted dates beside it.
  3. Save, then attach it to a job on the job editor's Frequencies tab.

The full steps are on Define a frequency.

Notes
  • Working days come from each workflow's Working Days, not a fixed Monday to Friday.
  • A working-day match that lands on a non-working day moves to the previous working day unless If date is non-working day says otherwise. A pattern whose day type is Day (Any day on a weekday pattern) runs on the date regardless.
  • Offsets count working days: 0 to 30 for weekly, −30 to 30 for monthly, quarterly, yearly and Annual Plan.
  • Quarters are calendar quarters, starting 1 January, 1 April, 1 July and 1 October. A weekday ordinal counts across the whole quarter.
  • A yearly weekday pattern counts across the whole year, from 1 January (or back from 31 December for Last), so it runs once a year.
  • A monthly Day pattern can pick several days, and with Day it offers If date is non-working day, unset meaning Keep the date (run anyway).
  • An Annual Plan runs on every plan date, holidays included; only its offset steps around holidays.
Watch out
  • The dialog's forecast uses the working days and holiday choice set in the dialog, so it can disagree with the build for a workflow with a different working week or an additional holiday calendar.
  • A workflow whose only qualifying work is On Request does not build at all.
  • An Annual Plan whose calendar was deleted or no longer resolves produces no dates, and nothing on the frequency says why.
  • A frequency a Vision card monitors, or that jobs use, cannot be deleted. Cross Reference counts the card but does not name it.
  • Renaming a frequency that jobs use stops their deployed workflows from building until each job is given the renamed frequency and the workflow is deployed again.
  • Deleting a frequency or a plan calendar and recreating it under the same name does not move references to the new one; the next save of a workflow or frequency that requires it is refused.
  • A monthly Day pattern for the 29th, 30th or 31st produces no run in a month without that day. Use Last · Day or Last · Working Day for the month end.