Frequencies
- Synopsis
- Full Details
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
- Open the Frequencies tab of the Toolkit and select New Frequency.
- Name it, choose the time period and the pattern, and check the highlighted dates beside it.
- Save, then attach it to a job on the job editor's Frequencies tab.
The full steps are on Define a frequency.
- 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:
0to30for weekly,−30to30for 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.
- 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.
Frequencies are global (not workspace-scoped).
Task walkthrough: Define a frequency. This page is the full configuration and troubleshooting reference.
A frequency is a named scheduling rule (a pattern) that decides which calendar dates a job is eligible to run on. Jobs reference frequencies; the per-job runtime settings (build status, timing, retries) live with the job (see Scheduling and the run).
- Patterns
- Quarterly and Yearly
- On Request and Annual Plan
- Working Days and Offsets
- Frequency List
- Forecast
Patterns
Pattern model
A pattern is defined by a time period and, for most, a selection under On:
-
Time period: the editor's Repeat field — Daily, Weekly, Monthly, Quarterly, Yearly, On Request and Annual Plan.
-
Selection: each period's On section offers up to three kinds of choice, which this page calls by date, by weekday and by period:
- by date — a specific day: the Day row of a monthly pattern (one or more days of the month, read as Day or Working Day), or the month and day of a yearly pattern.
- by weekday — named weekdays: the row of day buttons (S M T W T F S) on a weekly pattern, or an ordinal (First … Fifth, Last) with Weekday and day buttons on a monthly, quarterly or yearly pattern.
- by period — a period boundary: First or Last (and, on monthly, quarterly and yearly patterns, Middle) with Day or Working Day.
Daily, On Request, and Annual Plan have no selection — and On Request and Annual Plan have no interval either. Quarterly has no by-date selection.
| Pattern | Fields |
|---|---|
| Daily | Every N days, Start date (required) |
| Weekly · by weekday | Every, and the day buttons (e.g. Mon/Wed/Fri) |
| Weekly · by period | Every, First or Last, Offset days (0…30) |
| Monthly · by date | Every, and one or more days of the month (1–31) — a day the month does not have is skipped |
| Monthly · by weekday | Every, the ordinal (First … Fifth, Last), and one or more day buttons — e.g. "second Tuesday and second Thursday" |
| Monthly · by period | Every, First, Middle or Last, Offset days (−30…30) — e.g. "last working day" |
| Quarterly · by weekday | Every, the ordinal (First … Fifth, Last), and one or more day buttons — counted across the whole quarter |
| Quarterly · by period | Every, First, Middle or Last, Offset days (−30…30) — e.g. "last working day of the quarter" |
| Yearly · by date | Every, the month (January–December) and day of the month, If date is non-working day (required) — a day the month does not have runs on its last day, so 29 February runs on 28 February in a common year |
| Yearly · by weekday | Every, the ordinal, and one or more day buttons — counted across the whole year, so it runs once a year |
| Yearly · by period | Every, First, Middle or Last, Offset days (−30…30) |
| On Request | (none) |
| Annual Plan | Plan calendar (required) — one of your calendars, or Master Holiday Calendar (system) — and Offset days (−30…30) |
Several days in one pattern
A monthly, quarterly or yearly pattern can name more than one day, so "the 1st and the 15th" or "the first Monday and the first Friday" is one frequency rather than two.
Several days of the month. On a Monthly pattern, the Day list takes as many days from 1 to 31 as you need. Each day you pick is its own occurrence, read with the day type beside it:
- Day — that calendar day. A day the month does not have is skipped: the 31st produces no run in April, and the 30th none in February. Earlier builds moved it to the last day of the month instead.
- Working Day — that working day of the month: picking
1and10runs on the first and the tenth working day. A month with fewer working days than a number you picked produces no run for that number.
At least one day stays picked; the list does not let you remove the last one. Two picked days that land on the same date run once on it.
Several weekdays. On the ordinal row of a Monthly, Quarterly or Yearly pattern, choose First to Fifth or Last, then Weekday, and a row of seven day buttons (S M T W T F S) appears. Select every weekday you want: Second · Weekday with T (Tuesday) and T (Thursday) selected runs on the second Tuesday and the second Thursday. At least one weekday stays selected. Changing the ordinal keeps the weekdays you picked.
The second list on that row offers Weekday with every ordinal except Middle; First and Last also offer Day and Working Day (the start or end of the period), and Middle offers only those two.
Earlier builds ran a monthly Day pattern for the 29th, 30th or 31st on the last day of a shorter month. It now produces no run in a month that does not have that day. For "the 31st, or the last day of the month", use Last · Day (or Last · Working Day) instead.
Quarterly and Yearly
Quarterly patterns
Quarters are calendar quarters: January to March, April to June, July to September and October to December. There is no fiscal-year setting; a quarter always starts on 1 January, 1 April, 1 July or 1 October.
A Quarterly pattern has one On row, the same ordinal row as a monthly pattern, and no day-of-quarter choice:
| On | Runs on |
|---|---|
| First … Fifth · Weekday, with one or more weekdays | That occurrence of each weekday in the quarter, counted from the quarter's first day — Second · Weekday · M is the second Monday on or after 1 January, 1 April, 1 July or 1 October. |
| Last · Weekday | The last occurrence of each weekday in the quarter, counted back from its last day. |
| First · Day / Working Day | The quarter's first day, or its first working day. |
| Middle · Day / Working Day | The quarter's middle calendar day (15 November in October to December), or its middle working day. |
| Last · Day / Working Day | The quarter's last day, or its last working day. |
The ordinal counts across the whole quarter, not within its first month: Fifth · Weekday · F is the fifth Friday of the quarter, which can fall in its second month. Every quarter has at least twelve of each weekday, so Fifth always exists.
Choosing Quarterly starts the pattern on First · Working Day, also when you switch from another period. The switch keeps that period's interval and exclusion calendar, but not its day type. Earlier builds kept the day type too, so a new frequency, which starts as a daily pattern on any day, switched to Quarterly on First · Day.
Switching away does not carry that starting Working Day either. The Working Day a by period selection holds on a Monthly, Quarterly or Yearly pattern stays behind when you change the time period, so a new frequency taken to Quarterly and back to Daily, Weekly or Monthly is on any day again, with no non-working-day action. A Day you picked on a by period selection, and a day type on any other selection, still carries. Earlier builds carried the Working Day too, so that round trip quietly turned the pattern into a working-day pattern.
Every N quarters is counted on a fixed cadence of calendar quarters, not from the day you create the frequency. Every 2 quarters runs in January to March and July to September.
Non-working days and options work as on the matching monthly selections:
- Weekday patterns show Day type (Any day / Working days only). With Working days only, If date is non-working day decides where an occurrence on a non-working day goes, with the same default and choices as everywhere else (see When a working-day match lands on a non-working day). A move can carry the run into the neighbouring quarter: when the first Monday is 1 January and a holiday, Skip to previous working day runs it in the last days of December.
- Day and Working Day anchors take no action, because the anchor already lands where you asked. With Working Day, First and Last take Offset days (−30 to 30, counted in working days); Middle takes none.
- Both selections take an exclusion calendar.
A quarterly frequency is listed with type Quarterly in the Toolkit, and can be found with the Quarterly time-period filter in search and the Quarterly choice of the Frequencies report's Type filter.
Yearly weekday patterns
A Yearly pattern's ordinal row counts across the whole year, not within a month, and the editor says so under the row: Counted across the year: from January 1, or back from December 31 for Last.
| On | Runs on |
|---|---|
| First … Fifth · Weekday, with one or more weekdays | That occurrence of each weekday in the year, counted from 1 January — First · Weekday · M is the first Monday of the year, and Fifth · Weekday · M falls in late January or early February. |
| Last · Weekday | The last occurrence of each weekday in the year, counted back from 31 December. |
So a yearly weekday pattern runs once a year for each weekday you pick, in each year its Every interval admits. The pattern has no month, so a date such as "the fourth Thursday of November" cannot be expressed as a yearly weekday pattern.
Day type and If date is non-working day apply as on the other weekday patterns, and a move can carry the run into the neighbouring year: when the first Monday is a holiday on 1 January, Skip to previous working day runs it at the end of December.
Earlier builds ran a yearly weekday pattern in every month of a qualifying year: First · Weekday · M ran on the first Monday of each of the twelve months. It now runs once a year, in the build, the workflow editor's Forecast view, the Frequencies dialog's forecast and the Frequencies report alike. If you relied on the monthly runs, use a Monthly pattern instead.
On Request and Annual Plan
These two periods do not describe a recurrence. Each replaces the pattern with something simpler, and neither takes an interval, a day type, or a non-working-day action.
On Request
On Request takes no parameters at all. The editor says only Runs only when requested. Every day is eligible; automatic schedules skip it.
Every day qualifies for it, but the build never picks it up. A job whose only frequency is On Request is excluded from every scheduled build; an operator adds it to an instance that already exists, using Add Job. That exclusion is deliberate, not a gap.
One consequence is worth planning around: because the build skips On Request work, a workflow whose only eligible work is On Request has nothing to build, and the build fails rather than creating an empty instance. Give the workflow at least one job on a scheduling frequency if you need an instance to exist for On Request jobs to be added into.
Annual Plan
Annual Plan takes a required calendar reference and an optional offset. The calendar's dates are the qualified days — there is no recurrence rule to evaluate. The editor labels the field Plan calendar.
Save is blocked until you pick a calendar — the field reads A plan calendar is required — because a plan with no calendar has no dates.
The plan can be your Master Holiday Calendar. The Plan calendar list offers Master Holiday Calendar (system) first, above your own calendars. Choose it and the plan's dates are the dates of your organization's Master Holiday Calendar — a job that runs on each holiday, without keeping a second copy of the list. The plan reads the Master Holiday Calendar as it stands each time a build runs, so a date added there or removed reaches the next build without a redeploy, and it does so whether or not the workflow has Use Master Holiday Calendar on. A Master Holiday Calendar nobody has filled in gives the plan no dates. The option is offered for the Plan calendar only, never as an Exclusion calendar, and a calendar of your own that happens to be named Master Holiday Calendar stays a separate entry in the list.
An Annual Plan carries no day type and no non-working-day action — the pattern has no such field at all. A plan date that falls on a Saturday, a Sunday, or any other non-working day still runs. That is decided behavior, not an oversight: you put the date in the calendar, so the plan takes you at your word.
Holidays do not remove a plan date either. A plan date that is also a holiday for the workflow — on its Additional Holiday Calendar or, when it uses it, the Master Holiday Calendar — still runs. A plan whose dates are the holidays themselves therefore runs on each holiday. Earlier builds omitted a plan date that was a workflow holiday, so a plan like that never ran at all.
Offset days shifts each run relative to its own plan date, counting working days —
negative for before, positive for after, up to 30 either way. It does not reindex the plan: with
an offset of 1, plan dates 5 January, 10 February and 15 March each run one working day after
their own date, not on the next plan entry. The offset is the one place holidays matter to an Annual
Plan: each step skips holidays as well as non-working days, so a plan of holidays with an offset of
1 runs on the working day after each holiday.
The plan's calendar reference is now stored by id as well as name, and it is what protects the schedule from ordinary maintenance:
- Renaming the calendar is safe. The id identifies it, so the frequency editor shows the new name as soon as you open the frequency, and an automation export carries it. The name stored beside it is refreshed the next time the frequency is saved.
- Deleting it is refused. A calendar an Annual Plan is built on counts as in use, so the delete is blocked rather than quietly emptying the schedule. See Calendars.
- A reference that arrived from another environment heals. An imported frequency carries the source environment's calendar id, which means nothing here; saving repairs it from the name. Only a reference whose name is also gone is an error, and that error blocks the save rather than letting the frequency stand with no dates.
- A deleted plan calendar is not replaced by a namesake. If the plan's calendar was deleted and another calendar has since been created under its name, saving the frequency — or importing it — is refused with Calendar 'X' is deleted. Restore it or use a different calendar., and the build takes no dates from the new calendar. Restore the deleted calendar, or pick the new one as the Plan calendar. An exclusion calendar is optional, so a deleted one is left as stored and the frequency still saves.
If the reference resolves to nothing — a calendar removed directly, or a plan that never had one — the pattern qualifies no dates and the job simply never builds. Nothing on the frequency itself says why. If an Annual Plan job goes quiet, check its calendar first.
Working Days and Offsets
Shared options
These apply to the five recurrence periods (daily, weekly, monthly, quarterly, yearly). On Request takes none of them, and Annual Plan takes only its own offset. Yearly · by date is the one recurrence selection with neither a day type nor an Exclusion calendar: it takes only its required If date is non-working day.
| Option | Values | Notes |
|---|---|---|
| Day type | Working Day / Day (on a by-weekday selection, the Day type field: Working days only / Any day) | Whether the pattern counts only working days. |
| If date is non-working day (on Yearly · by date too) | Skip to next working day / Skip to previous working day / Keep the date (run anyway) / Omit (do not run) | What to do when a match lands on a non-working day. A non-working day is one of the workflow's non-working weekdays or one of its holidays (the Master Holiday Calendar and Additional Holidays); an Exclusion calendar removes dates afterward without moving them. The dialog shows a short help line with the field: Choose what happens on a non-working day. Skip runs on the previous or next working day. Keep runs on the non-working day. Omit drops the run. Consulted when the day type is Working Day — except on Monthly · by date, where it is consulted only when the day type is Day — and only on the selections listed below. |
| Exclusion calendar | a calendar | Dates to exclude (see Calendars). |
Working days and non-working days
What counts as a working day is the workflow's decision, not a fixed Monday-to-Friday. Each workflow sets its own Working Days (see Scheduling and the run), so under a Tuesday-to-Saturday week, Saturday is a working day and Monday is not. A working day is a day in that set that is not on a holiday calendar the workflow applies.
The day type decides whether the pattern cares:
| Day type | What it means |
|---|---|
| Day (Any day) | The configured calendar date, full stop. It runs there whether or not that day is a working day, and If date is non-working day is not consulted — with one exception, Monthly · by date, below. |
| Working Day (Working days only) | The pattern counts working days, and the emitted date is always a working day. |
When a working-day match lands on a non-working day
If date is non-working day decides, and the default is to move back to the previous working day:
| Action | Result |
|---|---|
| (not set) | Move to the previous working day — the run is preserved rather than lost. This is the default. |
| Skip to previous working day | The same, said explicitly. |
| Skip to next working day | Move to the next working day. |
| Keep the date (run anyway) | Run on the original date even though it is non-working. |
| Omit (do not run) | Drop this occurrence — the run does not happen. |
A Working Day pattern with no action configured used to silently produce no run for that occurrence: the date failed the working-day filter and disappeared. It now shifts back. If you were relying on that silence to suppress a run, say so explicitly with Omit (do not run) — otherwise the run you never saw will now appear on the previous working day.
Where the action is offered
If date is non-working day appears only on the selections where the action can actually change the date:
| Selection | Action offered | Why |
|---|---|---|
| Daily, Working Day | Yes | A daily match can land on a non-working day. |
| Any by weekday selection (weekly, monthly, quarterly, yearly), Working days only | Yes | "Second Tuesday" can land on a holiday. |
| Yearly · by date | Yes — and it is required, so the pattern always names one | A fixed date such as 31 December can fall on a weekend. |
| Monthly · by date, Day | Yes — and unset means Keep the date (run anyway) | "The 15th, or the working day before it" is a picked day that can fall on a weekend. The action applies to each day you picked. |
| Monthly · by date, Working Day | No | The pattern counts working days, so the date it produces already is one. |
| Any by period selection | No | The anchor resolves to a working day, and each offset step lands on one, so there is nothing to shift. |
| On Request, Annual Plan | No | The pattern has no such field. |
| Any other selection with the day type Day (Any day) | No | The action is not consulted. |
Monthly · by date with Day is the one place an unset action keeps the date. Its field shows Keep the date (run anyway) when the pattern names none, because that is what the build does, so the new field moves no run you already had. Choose Skip to previous working day for "the 15th, or the Friday before", or Omit (do not run) to drop a picked day that is not a working day. A move can carry a run into the neighbouring month — the 1st on a Saturday, moved back, runs on the previous month's last working day. Any action an older monthly Day pattern carried without showing it has been removed, so it cannot start moving or dropping runs. (A picked day the month lacks is a separate change — see Several days in one pattern.)
There is no "None" choice. A Working Day pattern always has an action: the field shows Skip to previous working day when the pattern names none, because that is what the build will do, and the editor records it explicitly when you switch the day type to Working Day (Working days only on a weekday pattern). Switching back to Day (Any day) clears it, and so does switching to a selection that does not offer the action. A cleared action stays cleared when you then change the time period. Earlier builds cleared it only from the day-type control, so an action cleared any other way could come back in the next time period — on Yearly · by date, a cleared Omit came back and dropped runs.
- Setting the action on a monthly Day N / Working Day pattern was offered and then rejected on save with Validation failed. The control is no longer offered there, and a stale value carried over from an older pattern is dropped when you switch the day type, so the save goes through.
- The action was offered on the by period selections, where it was accepted and then never applied — a setting that silently did nothing. It is no longer offered there.
- The list's None choice read as "do nothing" and behaved as "move to the previous working day". A pattern saved with None has not changed behavior; it now displays what it does.
The search for a working day is bounded at 30 days in either direction, so a match with no working day within reach is not searched for indefinitely.
A monthly Working Day count the month cannot reach produces no occurrence — "the fifth working day of this month" simply does not exist in a month with four, and nothing is substituted for it.
Offsets
The by period selections anchor to a period boundary — First, Last, and for monthly, quarterly and yearly also Middle — and Offset days steps away from that anchor.
Offsets count working days, not calendar days. Each step lands on a working day, so the result is always a working day too. Two things follow:
- A non-working-day action can never fire on an offset result. There is nothing for it to rescue.
- A day is skipped only if it is non-working for that workflow. Saturday is not inherently skipped: under a Tuesday-to-Saturday week the step counts it.
| Selection | Offset range |
|---|---|
| Weekly · by period | 0 … 30 — forward only |
| Monthly · by period | −30 … 30 |
| Quarterly · by period | −30 … 30 |
| Yearly · by period | −30 … 30 |
| Annual Plan | −30 … 30 |
An offset applies to the First and Last anchors only. A monthly, quarterly or yearly pattern
anchored on Middle takes no offset: the editor does not offer the field there, and a stored offset other than
0 is refused when the frequency is saved.
Because the offset traverses working days, the offset control appears only when the day type is Working Day. On a Day pattern there is no working-day sequence to step along and the engine ignores the value, so offering the field would let you configure something that silently does nothing. Switching the day type back to Day clears the offset.
Weekly · by period now has an Offset days field. Earlier builds applied a weekly offset if one was
stored but gave you nowhere to enter it, so the capability was reachable only through the API. Unlike
monthly, quarterly and yearly, weekly takes no negative offset — the field is clamped to 0–30 and the
editor says so, because it is the one selection whose range is one-sided.
For a Working Day pattern the anchors are working days too: First is the period's first working day, Last its last, and Middle its middle working day — not the middle calendar day nudged onto a working one.
A calendar-day offset landed wherever it landed, and if that was a Saturday the working-day filter dropped the occurrence — so in a month whose first working day was a Thursday, the job silently never ran. Counting working days is what makes the pattern mean what it reads like.
Frequency List
Working with the frequency list
The Frequencies tab of the Toolkit is a single list, and a frequency is created, edited and viewed in one dialog over it. There is no frequency detail page.
| Column | Notes |
|---|---|
| Name | The list's search box sits on this column. |
| Description | — |
| Type | The recurrence period — Daily, Weekly, Monthly, Quarterly, Yearly, On Request or Annual Plan. Sorts. |
| Interval | The repeat, read in the units the type implies (Every 2 weeks, Every 2 quarters, and so on). Shows — when the interval is 1, and for a type that has no interval. |
| Created / Updated | Sort. |
The dialog puts the form on the left — Name, Description and the Recurrence Pattern — and the forecast alongside it. Save turns on only once you have changed something and the pattern is complete, and closing with unsaved edits asks first. The dialog applies the same pattern rules as the forecast and the Frequencies report, so a pattern you can save is one the forecast can calculate. Two fields say what is missing themselves: an Annual Plan with no Plan calendar (A plan calendar is required), and a Daily pattern whose Start date you cleared (A start date is required). Anything else is named under the pattern:
| Under the pattern | When |
|---|---|
| Select at least one day of the week. | A by-weekday pattern has no day chosen |
| Select each day of the week only once. | A day of the week is chosen twice |
| Select at least one day of the month. | A monthly by-date pattern has no day chosen |
| Select days of the month from 1 to 31, each only once. | A day of the month is outside 1 to 31, or repeated |
| Enter offset days from -30 to 30. | Offset days is outside its range |
| Enter an interval of 1 or more. | The repeat interval is missing or below 1 |
| Complete the recurrence pattern. | Any other part of the pattern is missing |
While a pattern is incomplete, the forecast is not calculated either. Delete sits in the dialog's own footer, so you can reach it from a link straight to the frequency without finding its row.
Every editor action keeps the list's search, sort and page, so closing the dialog puts you back where you were.
What refers to a frequency
The frequency list's Cross Reference action shows both places a frequency can be used:
| Section | What it lists |
|---|---|
| Workflows | Workflows whose schedule carries this frequency, outside any job. |
| Jobs | Jobs that use it, shown as workflow: job: a job given the frequency on its Frequencies tab, and a job that names it as a dependency's predecessor frequency or an event's frequency. |
A job's Frequencies tab holds each frequency by its name, so that match is exact: the same letters, in the same case. Saving a workflow already refuses a job frequency whose name differs from the frequency's, even only in case, so every saved job is found.
A frequency that jobs use cannot be deleted. The delete is refused for as long as any job still has it, as it is for a workflow that uses it. Earlier builds missed jobs given the frequency on their Frequencies tab, which is where the job editor puts it: Cross Reference listed no jobs for a frequency that jobs used, and the frequency could be deleted from under them.
When there are more references than the dialog was given it says Showing N of M references rather than presenting a first page as the whole set.
A job holds the frequency on its Frequencies tab by name, and a deployed workflow's build looks that name up. After a rename the build finds no frequency of the old name and fails. Pick the renamed frequency on each job's Frequencies tab, save the workflow and deploy it again. Use Cross Reference to find the jobs before you rename. A workflow's own frequencies, set outside any job, are held by identity and keep building after a rename; earlier builds dropped their jobs from the build once the frequency was renamed.
A frequency a Vision card monitors is in use too. A Vision card that watches a frequency counts as a reference to it, so the frequency cannot be deleted while the card does, just as it cannot while a workflow uses it. Cross Reference and the delete confirmation count such cards in their totals but do not list them by name: the dialog reads Showing N of M references, and the blocked delete ends its list with …and N more. Only the cards you may view are counted there; the delete itself is refused whichever cards you can see. A card saved before this release with a frequency named but not identified does not hold the frequency until the card is saved again.
A workflow holds each frequency reference by the frequency's identity, with its name beside it, and every save checks it. A renamed frequency is still found, and its stored name is refreshed. A frequency that has been deleted is never swapped for a new one of the same name:
| Reference | When its frequency is deleted |
|---|---|
| The workflow's own frequencies | Required: the save is refused with Frequency 'X' is deleted. Restore it or use a different frequency. |
| A dependency's predecessor frequency, or an event's frequency | Optional: left as stored, and the save goes through |
Cross Reference and the delete check match these references by that stored identity, and a job's own frequencies by name, as above. A workflow last saved before this release can hold an identity that was never checked, and is not listed against the frequency it means until it is saved again. See Renaming or replacing an object a workflow uses.
Forecast
The frequency dialog shows the forecast beside the pattern you are editing: twelve month grids for one year, with the dates the pattern matches highlighted, and arrows to step a year at a time. It recalculates a moment after you change the pattern, so you can see its shape as you edit. While it works — including while it looks for the first year with a run — it shows Loading preview… and keeps the previous dates on screen. It is not recalculated when you return to the browser window from somewhere else, and when you open an existing frequency it waits until that frequency has loaded. The forecast is read-only — selecting a day does nothing.
Above the grids the dialog lets you choose what the forecast assumes: the Working Days and Use Master Holiday Calendar. They start as a new workflow does, Monday to Friday with the Master Holiday Calendar on, and the forecast recalculates when you change them. They only change the preview, never the frequency, and the dialog remembers your choice in your browser. See The dialog's forecast and the build.
The forecast opens on the first year with a run. When the dialog opens, and when you change the pattern, the forecast moves to the first year — from the current year, looking at it and the nine years after it — in which the pattern has a date. If none of those years has one, it stays on the current year. Once you have stepped to a year yourself, a pattern change keeps you there unless it leaves that year empty.
This one answers which dates does this pattern match? — one frequency, many dates. The workflow editor's Forecast view answers the other direction: on one date, which jobs would build, and when would each start? Both use the calculation the build uses, but only the Forecast view knows the workflow, so only it applies the workflow's working days and holiday calendars. Use this to see a pattern's dates, and the Forecast view to confirm what a workflow will build.
Earlier builds put it on a separate frequency detail page, which no longer exists; see Working with the frequency list.
The dialog's forecast and the build
The forecast in the Frequencies dialog is calculated by the same forecast calculation the build uses, so it reads the pattern exactly as the build does: the non-working-day action, the pattern's exclusion calendar, offsets counted in working days, the middle working day, and an Annual Plan's calendar and offset. What it cannot know is the workflow, because a frequency belongs to none. It differs from a build in two ways only:
| The dialog's forecast | The build |
|---|---|
| Uses the Working Days set above the grids, Monday to Friday to begin with. | Uses the workflow's own Working Days. |
| Applies the Master Holiday Calendar when Use Master Holiday Calendar is on, and no Additional Holiday Calendar. | Applies the workflow's holiday calendars: the Master Holiday Calendar, if the workflow uses it, and its additional calendar. |
If the Master Holiday Calendar cannot be loaded, the dialog says so and tells you to turn the switch off to preview without it.
So a frequency used by a workflow with a different working week, or with an additional holiday calendar, can still land on different dates in the build. To see what will actually build — working days and holidays included — use the workflow editor's Forecast view.
Earlier builds calculated this forecast in your browser with a simpler calculation of its own. It ignored the non-working-day action and the exclusion calendar, counted offsets in calendar days, and showed an Annual Plan's dates without its offset — so it could highlight dates the job would never run on, such as a Saturday for a yearly date set to Skip to previous working day. If you checked a pattern against the old forecast, check it again.
Two periods read differently in the dialog's forecast:
- On Request highlights every day, because every day qualifies for the pattern. It is not telling you the job runs daily — the build never selects an On Request frequency at all.
- Annual Plan highlights the plan calendar's dates — or, on Master Holiday Calendar (system), the Master Holiday Calendar's — for the selected year, each moved by the offset when there is one. An empty forecast for an Annual Plan means the calendar has no dates that year, or that the calendar was deleted or can no longer be found — which is also what the build does with it.
When the forecast cannot be shown
| Message | What it means |
|---|---|
| Preview unavailable — A calendar this frequency uses could not be loaded. It may have been deleted, or you may not have permission to view it. | The pattern's exclusion calendar could not be read, or an Annual Plan's Plan calendar exists but could not be read, for example because you may not view it. Earlier builds showed an empty forecast for an unreadable plan calendar, although the build, which still gets its dates, would run on them. |
| Preview unavailable — The forecast could not be loaded. You can still save the frequency. | The forecast did not answer. Saving the frequency is not affected. Earlier builds also showed this for a Daily pattern with its Start date cleared, which could not be saved either; that pattern now shows A start date is required and no forecast. |
Limits on a forecast
These limits belong to the forecast calculation the build, the workflow editor's Forecast view and the Frequencies dialog use, and they bound each request so a single pattern cannot monopolise it. The Frequencies dialog asks for one calendar year at a time, which keeps it inside the date-range limit.
| Limit | Value |
|---|---|
| Date range | The end date at most 365 days after the start date — 366 days, counting both ends |
| Calendar year of any date asked about | 1900–2999 |
| Offset days, any pattern | ±30 |
| Days named by a weekly, monthly, quarterly or yearly by-weekday pattern | at most the seven day names, each named once |
| Days of the month named by a monthly Day pattern | at most 31, each a number from 1 to 31, named once |
| Working days on a schedule | at most the seven day names |
| Annual Plan dates supplied directly in a request | 1,000 |
| Holiday dates supplied directly in a request | 1,000 |
The two 1,000-date caps apply only to dates written into a request itself. A calendar the platform looks up for you — every calendar a workflow or frequency names, which is how the build works — is not capped, and neither are exclusion dates. An Annual Plan calendar can hold more than 1,000 dates: the build for a date uses only the plan dates that can land on it, given the plan's offset. Earlier builds failed for every date of a workflow whose Annual Plan calendar held more than 1,000 dates, although the forecast showed nothing wrong.
A request beyond these is refused with an error rather than calculated slowly. The same ±30 offset bound is enforced when you save the frequency, so a pattern that forecasts will also save.
The year window is shared with the build, so a workflow cannot be built for a schedule date
outside 1900–2999 either — the date is refused where you enter it rather than failing later in the
build. Dates are held as YYYY-MM-DD throughout, and a four-digit year is what makes them sort and
step correctly; the window is where that holds.
A by-weekday pattern that names the same day twice is refused rather than quietly deduplicated, and so is one naming something that is not a day of the week. Both were previously accepted without comment, which meant a typo'd day name simply had no effect on the dates instead of being reported.
- A frequency is the pattern; when within the day and retry/rerun behavior are the job's per-frequency runtime settings, not the frequency itself.
- The Frequencies dialog's forecast uses the working days and Master Holiday Calendar choice you set there, Monday to Friday with holidays on to begin with, because a frequency belongs to no workflow, so it can disagree with the build for a workflow with a different week or an additional holiday calendar. The workflow editor's Forecast view applies both — check a workflow there before relying on a date. See The dialog's forecast and the build.
- In the build, a daily every-N-days pattern no longer repeats a date across a daylight-saving change. The cadence is recomputed from each date rather than advanced by a fixed number of hours, so the 23-hour day that used to emit the same date twice no longer can.
- New frequencies default to a daily, interval 1, any-day pattern, with a start date of 1 January of the current year rather than today. That fixed anchor is what makes an every N days pattern land on predictable dates — with a start date of "today" the same interval produced a different set of dates depending on when you created it — and it means the forecast for a new pattern covers the whole year rather than only the part of it still to come.