Vision (critical-path monitoring & SLAs)
This feature is still being finalized by Development.
- Synopsis
- Full Details
In briefVision watches whether the right work finishes on time. A board is a tree of cards: a tag card follows the jobs whose tags match its pattern, in one source environment, for a schedule date, and checks them against SLA targets; a group card rolls up its children. Each card shows one status icon, and its hover panel names the status, from Late and At risk through Finished.
WhereVision, at the top of the navigation, shows the Live board for a Workflow Date. Design › Vision Config is where cards are created, edited and deleted.
When
- You want to see at a glance whether a critical set of jobs will meet its deadline.
- You are setting a start or end SLA on a group of jobs that share a tag.
- A card shows Unknown, No schedule date or Late and you need to know why.
How
- On Vision Config, select New Vision Card and create a tag card: Name, Source Environment, Tag(s) and at least one frequency that exists.
- Add SLAs to each frequency — SLA Requirement, Time in UTC and Day(s) Offset.
- Group related cards under a group card if you want a roll-up.
- Watch the cards on Vision, point at a card for its status and job counts, and use Processes to open the jobs behind it. The task walkthrough is Monitor critical paths and SLAs with Vision.
- The Vision board refreshes every 15 seconds; there are no push updates.
- Tag patterns accept
*and?and are case-sensitive. - An empty SLA list is valid: the card is monitored only.
- SLA times are compared in UTC, while Start and End on a card show the scheduler's time zone.
- Triggers are saved with the card, but trigger processing is off by default, so no action fires unless Continuous has turned it on for your organization.
- A card's source environment cannot be un-bound once set.
- A frequency a card monitors cannot be deleted until the card stops using it, and a group card cannot be deleted while it has child cards.
- Vision treats every day as a working day and applies no holidays, so a card can qualify on different days than its workflow runs.
Task walkthrough: Monitor critical paths and SLAs with Vision. This page is the full configuration and troubleshooting reference.
Vision monitors whether the right work is finishing on time, by tag, against service-level agreements (SLAs). A Vision board is a hierarchy of cards; Vision evaluates each card against a chosen schedule ("anchor") date and surfaces its status on the board.
- Cards
- How Evaluation Works
- The Interface
- Triggers
- Permissions
- Troubleshooting
Cards
Two card types (Type is chosen at creation and cannot be changed afterwards):
| Type | Purpose |
|---|---|
| Tag card | Monitors the jobs whose definition tags match a tag pattern, on a schedule date, in one source environment. |
| Group card | Carries no pattern or frequency of its own — rolls up the stats and state of its child cards. |
Cards form a tree through Parent Group: a child's parent must be a group card, and a card cannot be its own parent or sit in a cycle. A card's parent group must be in the same workspace as the card: setting a parent in another workspace is refused with Parent card must be in the same workspace as this card, and moving a group that has child cards to another workspace is refused until you move or detach its children. A card nested across workspaces before this rule stays editable; the rule is checked when its parent or workspace changes.
A group card that still has child cards cannot be deleted. The delete is refused with Cannot
delete VisionCard '<name>': has <n> references. Remove all references before deleting. Delete
its child cards, or move them to another group, first. If a card is being added under the group as
you delete it, the delete waits for that save to finish and is refused if the card was added.
Before that rule, a card could be added under a group in the moment the group was being deleted. Such a card was left under the deleted group: the board never showed it and its triggers never fired, though Vision Config still listed it as a top-level card. This release deletes those cards, together with any cards under them, so Vision Config no longer lists them.
Card configuration
The card dialog (New Vision Card or Edit Vision Card) shows these in this order, and saves with Save:
| Setting | Required | Default | Notes |
|---|---|---|---|
| Name | Yes | — | 3–255 characters |
| Type | Yes | Tag | Tag or Group. Cannot be changed after create |
| Parent Group | No | — None — | Must be a group card |
| Source Environment | Tag: Yes at create | — | The environment whose runtime supplies the card's job data. Cannot be un-bound once set. Group cards have none |
| Tag(s) | Tag: Yes | — | The card's tag pattern. Up to 255 characters. Exact, or */? wildcards. Case-sensitive: Nightly-* does not match a job tagged nightly-core. Group cards have none |
| Day(s) Offset | No | 0 | Tag cards only. Range −5..+5; resolves the card's schedule date to the Nth qualifying frequency day |
| Description | No | empty | |
| Frequencies | Tag: at least one | — | Priority-ordered: the first matching frequency claims the day. Drag the handle beside a frequency to change its place in the order. With none, the dialog says At least one frequency is required. Add to monitor this card & attach SLAs/triggers. Group cards have none |
Each frequency association on a tag card holds a frequency and a list of SLAs.
A card's frequencies must exist when you save it. Each frequency you add or change is looked up
when the card is saved, and the card stores that frequency's identity and current name. A frequency
that does not exist is refused with Frequency '<name>' not found, or you do not have permission to
view it., and one that has been deleted
with Frequency '<name>' is deleted. Restore it or use a different frequency. A frequency the
card already holds is not checked again, so a card whose frequency was deleted earlier can still be
edited and saved. A frequency that a card monitors cannot itself be deleted while the card uses it,
and the frequency's Cross Reference counts the card. See Frequencies.
SLA (per card × frequency)
| Setting | Required | Default | Notes |
|---|---|---|---|
| SLA Requirement | Yes | Expected end | Expected start or Expected end |
| Time | Yes | 00:00 | HH:mm, 24-hour |
| Day(s) Offset | Yes | 0 | Range −5..+5; a plain calendar-day offset on the target (the cross-midnight mechanism, e.g. end 02:00 +1 day) |
An empty SLA list is valid ("monitored only").
SLA times are in UTC. Vision compares each SLA against UTC, while the Start and End times on
a Live card are shown in the scheduler's time zone — so enter the deadline as its UTC time (for
example, a 06:00 deadline in US Eastern daylight time is 10:00).
How Evaluation Works
For an anchor date, the engine snapshots the whole board, and for each tag card: picks the qualifying frequency (priority order), resolves the schedule date (via the day-offset walk), resolves the card's source environment to that environment's runtime, and aggregates matched jobs by tag pattern + schedule date from that environment. Group cards roll up their children.
Which days a frequency qualifies. Vision works out a card's frequency days from the frequency's pattern, its Exclusion calendar and, for an Annual Plan, its Plan calendar (including an Annual Plan on the Master Holiday Calendar). It treats every day of the week as a working day and applies no holidays, so a frequency built on working days, or one that moves a match off a non-working day, can qualify different days on a card than in a workflow's build. Earlier builds ignored the exclusion calendar and never matched an Annual Plan. An Annual Plan whose calendar no longer exists qualifies no days. If a calendar a frequency uses cannot be read, a card that reaches that frequency shows Unknown: for an exclusion calendar, only on a day the frequency's pattern would otherwise qualify.
The day-offset walk reaches far enough for sparse frequencies. A Day(s) Offset counts qualifying days of the card's frequencies, so on a quarterly or yearly frequency, or one that runs every few months, an offset of 3 can sit many months from the anchor date. The walk goes as far as five years either side, so any offset up to ±5 resolves on a frequency that runs at least once a year. Earlier builds looked only about six months either side and showed No schedule date on such cards. A frequency that runs less often than once a year can still show No schedule date.
Matched jobs fall into five buckets, which a card's hover panel counts as Waiting, Running, Finished, Warning (jobs that did not run) and Error (jobs that failed). A card is evaluated on four independent signals, which the Live view sums up as one status icon and one status label (see The Live board):
| Signal | Values | Meaning |
|---|---|---|
| Progress | Waiting · In process · Finished, or none | Count-driven; none = no matched jobs |
| Severity | none · normal · warning · error | Warning = any job that did not run; error = any failed job |
| Conditions (several at once) | Failed · Partial failure · Finished OK · Late to start · Late to finish · Estimated late to start · Estimated late to finish | Count- and SLA/time-driven; a card can hold several at once. On-track SLA = no condition. These are the names a trigger's Trigger When Condition list uses, and it also offers Unknown |
| Lifecycle | Unknown · No schedule date | Takes the place of the signals above when set |
SLA logic: target = the schedule date at Time, plus the SLA's Day(s) Offset in calendar days (UTC). Breached (Late to start or Late to finish) when past target with nothing started/finished (or an actual is past target); at-risk (Estimated late to start or Estimated late to finish) when a forecast exceeds target but now is before it.
How often the board refreshes
The Live board (the Vision page) re-evaluates every 15 seconds while it is open, and each refresh updates the Updated time under the date picker, shown to the minute. There are no push updates.
Environment-awareness
Each tag card is bound to its own source environment, and environments are resolved on each evaluation. A card whose environment can't be used — unset, not registered, unhealthy or unresolvable — shows Unknown, rather than sinking the whole board.
The Interface
Vision has two pages, each with a header that names it above the line Tag-based critical-path monitoring & SLAs:
| Page | Where in the navigation | Address | What it is for |
|---|---|---|---|
| Vision | At the top, after Dashboard | /vision | The Live board |
| Vision Config | In Design, after Self Service Config | /vision/cards | Creating, editing and deleting cards |
Earlier builds reached the cards through a Live / Cards tab bar on the Vision page; that tab
bar is gone, and links to /vision/cards still open the card setup.
Vision Config lists every card you can view in one table, with New Vision Card, Edit and Delete above it:
| Column | What it shows |
|---|---|
| Name | The card's path: the groups above it and its own name, separated by > — for example Finance > Payroll > Nightly close. A card in no group shows its name alone |
| Type | Tag or Group |
| Contains | For a group card, how many cards sit directly under it (<n> cards); -- for a tag card |
| Day Offset | The card's Day(s) Offset, signed (+2, -1, 0) |
| Last Updated | The date the card was last saved |
- Search — the box in the Name heading keeps the cards whose path contains what you type, ignoring case, so searching for a group's name also finds every card under it.
- Sort — by any column; the list opens sorted by Name.
- Pages — 20 cards to a page by default.
- Select — selecting a row selects it. Edit opens the one selected card; Delete deletes every selected card, the deepest first, so selecting a group together with all its cards deletes them all. A card that cannot be deleted stays in the dialog, with the reason. Each row's menu also offers Edit and Delete.
Earlier builds showed one level of the tree at a time, with drill-down into a group and breadcrumbs back. The card dialog is described under Card configuration; each frequency in it carries its own SLAs and Triggers, with Add SLA, Add Trigger and Add Frequency below each list.
The Live board
- Workflow Date — the one date the board is evaluated for (default today). The Updated time under it shows when the board last refreshed.
- Layout — the top-level tag cards come first. Each top-level group card follows as a bordered
section headed Group:
<name>(<n>cards), holding its child cards; a group inside a group is a section nested inside it. Every level is on the page at once, so there is nothing to drill into. A group section shows no status of its own; its child cards show theirs. - No cards — with nothing to show for the date, the board says No Vision Cards found. No cards are scheduled or none have been configured.
Each card shows, from the top:
| Part | What it shows |
|---|---|
| Status icon and name | The icon sums up the card's state (below) |
| Path | Under the name: the groups the card sits in and its own name, separated by >, as on Vision Config |
| Environment badge | The card's source environment by name. When the environment cannot be used, the badge says why instead: No environment set, Environment has no runtime service, Environment unhealthy or Environment unavailable |
| Description | The card's Description, cut short after a few lines |
| Start, End, Duration | Actual start and end in the scheduler's time zone, and the time between them; — until there is a value. A warning mark beside Start or End shows which SLA is late or at risk |
| Processes | A button at the lower right. Opens Processes in Job View for the card's source environment, filtered by its tag pattern and schedule date. Offered only on a card with both a tag pattern and a source environment |
Selecting the card itself opens nothing: Processes is the way through to its jobs.
| Status icon | When |
|---|---|
| Question mark (grey) | Unknown or No schedule date |
| Red error mark | Any job failed, or an SLA was breached |
| Yellow warning mark | Any job did not run, or an SLA is at risk |
| Green check | Finished |
| Blue play mark | In process |
| Grey clock | Waiting, or no matched jobs |
The hover panel opens while the pointer is over a card or focus is inside it. It shows the card's status label and the Waiting, Running, Finished, Warning and Error counts. The status label is the first that applies in this order: Unknown or No schedule date; Late (any SLA breached); At risk (any SLA forecast to be missed); Failed; Partial failure; then Finished, In process or Waiting. A card with no matched jobs shows —.
Triggers
Each frequency association on a tag card carries a Trigger editor: a condition the card can hold, and one or more actions to take while it holds it. Triggers are saved with the card, but trigger processing is off by default and is not something you can turn on. Unless Continuous has turned it on for your organization, no action is taken when a card goes late or at risk. Read the card's status on the Vision board instead.
An action is an OpCon event — the same event taxonomy the rest of the platform uses. Vision does not have events of its own: the engine evaluates the condition and emits the action's event.
What an action holds
| Field | What it is |
|---|---|
| Event | The event type to fire, picked from the same catalogue the job editor and Self Service use: grouped by category, each name shown with its $TYPE code. A type that is not built yet is listed and disabled (Not yet available); a type the platform will never support is not listed at all |
| The type's own fields | Once a type is picked, the form renders that type's fields — one control per field, with the type's own required-field and value rules |
| Environment | Where the action's event is applied. The default is the card's source environment, named in the list so you can see which one that is |
| Repeat after (min) | Fire once more after this many minutes if the condition still holds. 1–60; leave it empty to fire once |
A rejected action is shown on the card. When trigger processing is on and the event service
refuses an action outright, the action is not retried, and the Live card shows a red marker under
its environment badge: Action rejected: followed by the event type and the condition, or
<n> actions rejected when there are several. Pointing at the marker shows each one with the
reason it was refused. The marker goes when a later repeat of the action is delivered, when the
condition has cleared and at least 10 minutes have passed since the action fired, on another
Workflow Date, or once you change the action, its trigger, the frequency or the card's source
environment. A failure that may pass, such as the event service being briefly unreachable, is
retried rather than shown.
Values can carry tokens. A field that takes text accepts a global property
token and, uniquely to Vision, a Card token — written [[CI.$…]] and
filled with the firing card's own values: Vision sends the card's values with the action's event,
and the event resolves the tokens as it is processed. The property selector offers them in a
Card group:
| Token | What it resolves to |
|---|---|
[[CI.$CARD NAME]] | The name of the card whose trigger fired |
[[CI.$CARD FREQUENCY NAME]] | The frequency the card is monitoring |
[[CI.$CARD STATUS]] | The condition the card holds, as its code: for example LATE_TO_FINISH for Late to finish |
[[CI.$CARD START TIME]] | Actual start time |
[[CI.$CARD END TIME]] | Actual end time |
[[CI.$SCHEDULE DATE]] | The schedule date the card is monitoring |
[[CI.$REMOTE INSTANCE NAME]] | The target environment, if any |
Card tokens have values only in a Vision action's event. They mean nothing in a job event or a notification, and nothing else in the platform supplies them.
A card value is one name, so it cannot add a separator to a tag list or a console message.
If a card token in the tags field of a tag event resolves to a name containing a comma or a
semicolon, the event fails rather than adding the pieces as separate tags. If a card token in the
Message of a $CONSOLE:DISPLAY event resolves to a name containing a comma, the event fails
too: that message keeps only the commas you type. The action editor warns about both when a field
holds a card name token ([[CI.$CARD NAME]], [[CI.$CARD FREQUENCY NAME]] or
[[CI.$REMOTE INSTANCE NAME]]):
| The token is in | The warning says |
|---|---|
| Tags | Tags uses commas and semicolons to separate values. If a value placed here contains either one, the event is refused. |
Message of $CONSOLE:DISPLAY | Message can hold a comma only as typed text. If a card name placed here contains a comma, the event is refused. |
Neither warning blocks Save. See An event raised from outside a job.
A token with no value resolves to its own name. A start or end time the card has only a forecast
for, and an absent remote instance, come through as the literal text CI.$CARD START TIME,
CI.$CARD END TIME or CI.$REMOTE INSTANCE NAME rather than as an empty string — so a message that
is missing a value says which value is missing instead of reading as though the field were blank.
This matches the legacy product.
Card names and frequency names reach the action exactly as they are, whatever characters they
contain. A card named Nightly [[OI.REGION]] puts that text into the action; the [[OI.REGION]]
inside the name is not resolved.
Earlier builds substituted the names into the action's text first and then resolved the whole thing, so a name that happened to contain token syntax was expanded as a property — and a card whose name held a token the platform did not recognise failed when it fired, with the action silently dropped. Global property tokens you write in the action yourself still resolve, in the same pass.
An unknown Card token is refused when the card is saved, with a message naming the token, so a
typo like [[CI.$CARD NAM]] is caught in the card dialog rather than at firing time. So is a Card
token that is not written correctly at all — an empty name, as in [[CI.]], a ( in the name, as
in [[CI.$CARD START TIME(+1dd)]], or an unclosed quote. The same holds for a Card token behind a
remote-instance prefix, such as [[RI.X.CI.]]. Earlier builds saved those, and the action
never ran. A card saved
before this check that still holds an unknown token fails when it fires, and the failure names the
token.
An action is checked against its event type before the card saves
Every action goes through the same event rules the job editor, Self Service and the event service apply, so an action that could never fire cannot be saved. Save stays disabled while any action is invalid, and the problems are reported per field. What is refused:
- An event type that is unknown, not supported, or not built yet.
- A required field of the type left empty.
- A value that the field cannot read — a non-number in a number field, a value outside an option list, a malformed date, a value over the field's length.
- A parameter the type does not have. A stored action can hold one, from before this check existed: the form lists it below the fields with its saved value and a Remove button, rather than ignoring it until it fails at fire time.
A saved action shows every problem the moment the card opens, so an action that no longer passes the rules says why the card cannot be saved. A new action reports a field's problem once you have touched that field.
One exception keeps an unrelated edit from being blocked: an action you have not changed, whose event type is listed but not built yet, is a warning rather than an error. Change its type or its values and it becomes an error like any other.
Commas you type are fine in a Vision action's values. Vision fires the event's named fields, never a command line, so there is no separator for a comma to break. A comma or semicolon that a card name brings in is the exception described under What an action holds.
Permissions
The Vision Cards row, on the role editor's Workspaces tab (workspace-scoped) — four permissions:
| Permission | Description |
|---|---|
| Vision Cards View | View Vision cards |
| Vision Cards Create | Create new Vision cards |
| Vision Cards Edit | Modify existing Vision cards |
| Vision Cards Delete | Delete Vision cards |
The Live view needs Vision Cards View as well. Each refresh of the board is checked against your roles, and it shows only the cards in workspaces your Vision Cards View grants reach. Opening Vision itself needs no permission.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| Card shows Unknown | Its source environment is unset, not registered, unhealthy or unreachable — or the environment is fine but its job data, or a calendar one of its frequencies uses, could not be read on this refresh | Check the card's source environment binding and that environment's runtime health (Administrator). If the card shows no environment error, wait for the next refresh. |
| Card shows No schedule date | The card's Day(s) Offset cannot be resolved: fewer than that many qualifying days of its frequency fall within about five years of the Workflow Date (as with a frequency that runs less often than once a year) | Check the card's frequencies and day offset (Builder). |
| Card missing from the Vision board | None of the card's frequencies covers the selected date (an On Request frequency never does, nor does an Annual Plan whose calendar no longer exists), or — for a group card — none of its children is shown | Check the card's frequencies, or pick another Workflow Date. |
| A card appears on a different day than its workflow runs | Vision treats every day as a working day and applies no holidays when it works out a frequency's days | Expected. Give the card a frequency whose pattern names the days you want, or an Exclusion calendar (Builder). |
| Card never matches jobs you expect | Tag patterns are case-sensitive | Match the tag's exact case in the pattern (Builder). |
| Card goes late at the wrong hour | SLA times are compared in UTC | Enter the SLA time in UTC (Builder). |
| Card status looks a few seconds old | The Live view refreshes every 15 seconds | Wait for the next refresh, or reload the page. |
| A trigger never runs | Trigger processing is off by default | Expected. Watch the card on the Vision board instead. |
| Processes not offered on a card | Card has no tag pattern or no bound source environment | Only tag cards with both offer Processes. |
| Card shows Action rejected | Trigger processing is on, and the event service refused the action | Point at the marker to read the reason, then correct the action on Vision Config (Builder). |
Save refused with Frequency '<name>' not found, or you do not have permission to view it. or is deleted | A frequency you added or changed on the card does not exist, or has been deleted | Pick a frequency that exists, or restore the deleted one (Builder). |
| Deleting a frequency is refused | A Vision card monitors it | Remove the frequency from the card on Vision Config first (Builder). |
Deleting a group card is refused with has <n> references | The group still has child cards | Delete its child cards or move them to another group first — or select the group and all its cards and delete them together (Builder). |
| Save refused with The card hierarchy was changed by another save at the same time or VisionCard was modified by another request | Another save moved or re-parented this card, or a card in its tree, at the same moment | Reload Vision Config and save again (Builder). |
Contact support when
- A card evaluates against the wrong environment or the wrong jobs, or its environment status is stuck.