Health
Whether the automation engine can process what the rules produce: the engine flag, its message queue, its worker, the outbox and run counts, and the scheduler's heartbeat.
Health
This page tells you whether automation is working: whether it is switched on, whether the queue that carries changes to it answers, whether what is waiting is being processed, and how many events and runs are in each state. Look here first when runs stay Pending or reminders stop going out.
Where to find it
Account menu > Settings > Workflows > Health, or Open Health at the end of the yellow engine warning shown on the other Workflows tabs.
Only people with the Edit permission on Workflow Rules (the Administrator in the default roles) see the tab. Anyone else who reaches the page sees "No access" and "You do not have permission to view workflow health. Ask your administrator."
What you see
The page header reads "Whether automation is running: the switch, the queue that carries changes, the processing of what is waiting, and the scheduler that runs timed rules." with "updated <time ago>" and a Refresh button. The page refreshes itself every 30 seconds.
Three status cards
Each card shows a headline in green, amber or red and a line of detail. A red or amber detail says what to do: usually wait a few minutes, and open a case with the NirmaanOne team if it does not clear. Nothing on this page names servers or settings; the NirmaanOne team reads the server side.
| Card | Headlines |
|---|---|
| Automation | On ("Automation is switched on: rules fire when records change.") or Off ("Automation is switched off on the server. Changes are kept and processed once it is switched on again; open a case with the NirmaanOne team."). |
| Queue | Connected ("The queue is answering and changes reach the automation."), Not set up ("The queue that carries changes to the automation is not set up, so nothing can run. Changes are kept meanwhile; open a case with the NirmaanOne team.") or Not answering ("The queue is not answering, so rules cannot run. Changes are kept and processed once it is back; if this lasts more than a few minutes, open a case with the NirmaanOne team."). |
| Processing | Idle ("Nothing waiting; the last change was picked up <time ago>." or "Nothing waiting; nothing to do."), Processing ("N changes being processed; the last was picked up <time ago>."), Quiet for a while ("N changes waiting and the last was picked up <time ago>. If this does not clear within a couple of minutes, open a case with the NirmaanOne team."), Nothing picked up yet ("Changes are waiting and none has been picked up yet. Give it a minute; if the backlog keeps growing, open a case with the NirmaanOne team."), Backlog is stuck ("The oldest change has waited N min although the queue answers, so processing has probably stopped. If it does not clear within a few minutes, open a case with the NirmaanOne team.") or Unknown ("Processing cannot be checked while the queue is not answering; that comes first."). |
Outbox
"Changes waiting for automation, by status. Click a count to list them." One row per outbox status (Pending, Dispatched, Processing, Processed, Failed) with its count; each count links to the Outbox filtered to that status. Underneath: Oldest pending (how long the oldest waiting event has waited, shown in red when it is over two minutes, or "none") and Last dispatched (how long ago, or "never").
Runs
"Rule executions, by status. Click a count to list them." One row per run status (Pending, Running, Waiting, Success, Blocked, Errored, Skipped) with its count; each links to Runs filtered to that status.
Scheduler
"Runs the timed rules and moves waiting changes along." Shows Last scheduled run (how long ago the scheduler last fired scheduled rules, or "never") and reminders of the timetable:
- "Waiting changes are picked up every 10 seconds."
- "Scheduled rules are checked every minute against their timing."
- "Due-date checks (due today, overdue and the like) run daily at 08:00 India time."
What you can do
Refresh
Fetches the latest figures at once instead of waiting for the next automatic refresh.
Count links
Each number in the Outbox and Runs cards opens the matching list filtered to that status, so an Errored count takes you straight to the runs that need attention.
Statuses
The cards use three colours: green (healthy), amber (worth watching: "Quiet for a while", "Nothing dispatched yet", "Unknown") and red (broken: "Disabled", "Not configured", "Unreachable", "Backlog is stuck").
Things to know
- What "healthy" looks like. Automation On, Queue Connected, Processing Idle or Processing, and Oldest pending "none" or a few seconds.
- Nothing is lost while automation is down. Rules are still saved and events are still written to the outbox; they are processed once automation, the queue or processing is back. Runs simply stay Pending until then.
- The daily due-date check is what raises the "Installment due (daily)" and "Demand overdue (daily)" events, so the overdue reminders and escalations fire once a day, at 08:00 India time, not the moment a demand becomes overdue.
- The Automation card can read On while nothing runs. It reports the on/off switch only; automation also needs the Queue to be connected. Read the three cards together.
- The other tabs warn too. Whenever the Automation or Queue card would be red, a yellow warning appears above the Rules, Event types, Message templates, Runs and Outbox tabs for people who can see this page. Stuck processing (Backlog is stuck) shows only here, so check this page when runs stay Pending although no warning appears.
- Nobody else can see this. Users without the Edit permission on Workflow Rules get no warning when automation is down; to them, runs just stay Pending. Check here when someone reports that an automation "did nothing".
Related
Related
- RunsScreen
Every time a rule ran: what started it, which record it worked on, how each action went, and the panel from which an errored run is retried.
- OutboxScreen
The events recorded when records change, on their way to the rules that listen to them, with the runs each event produced and the panel from which a failed event is requeued.
- RulesScreen
Every automation rule in your organization, system and custom, with filters, the switch that turns each rule on or off, and shortcuts to edit, test, clone, see the run history of or delete a rule.
- WorkflowsScreen
The Workflows area of Settings, where you manage automation rules, event types and message templates, and check the runs, the outbox and the engine's health.
- Investigate a failed automationHow-to
When a reminder, task or automatic run didn't happen, check that the workflow engine is working, find the run that failed and read its error, fix the cause, then retry the run or requeue the event.
- Workflow runs stay Pending: automation is off, its queue is down or processing has stoppedTroubleshooting
Rules keep saving and events keep being recorded, but nothing runs while automation is switched off on the server, the queue that carries changes to it is missing or down, or processing has stopped; the Health tab shows which, the NirmaanOne team fixes it, and the waiting work is then processed.