Monitoring
The Monitoring page answers one question: is production running normally right now, and if not, what needs attention?
It is a live view of today. It refreshes on its own every 20 seconds. For historical trends over weeks and months, use the Reporting page instead.
Monitoring covers production only, and only projects that have been published. A project still in design has nothing running to monitor, and the page says so rather than showing zeros.
Scope
The project selector in the title bar sets what you are looking at:
- A single project, the default.
- All projects, available to users who can monitor more than one project. This aggregates every published project you are allowed to see, and adds a per-project breakdown so the outlier is one glance away. Choosing it does not change your current project anywhere else in the app.
Controls
- Count by switches the funnel between counting transactions and counting documents. A transaction can contain many documents, so the two answer different questions. The choice is remembered per project.
- Compare to sets the baseline every funnel figure is measured against: yesterday, the same weekday last week, a 7-day average, or a 30-day average. The green or red figure under each number is today's difference from that baseline.
Reading the page
The sections are ordered so that the earlier one usually explains the later one. Work down, and report the first thing that is wrong rather than the loudest.
Import connectors
Live health of the project's published import connectors. Check this first. A feed that has stopped explains every zero further down the page, and a low document count on its own cannot tell you the difference between "quiet day" and "nothing has arrived since Tuesday".
Each connector shows its control state, its health, and when it last imported. Two signals are worth knowing:
- Paused means somebody turned it off deliberately. It is not a fault.
- Stale means the connector is polling happily with no errors, but nothing has arrived in a long time. A dead feed reports no errors at all, so this is the only signal that catches it.
With the right permission you can Pause, Resume, or Retry a failed item from here, without publishing anything.
This section hides itself when the project has no published connectors.
Today's funnel
Where today's work is, in four numbers:
| Received | Arrived today, by upload, connector, or API. |
| Auto-processed | Completed without needing a human. |
| Routed to review | Sent to a review step. |
| Completed | Finished today, whether automatically or after review. |
A funnel that is entirely zero usually means intake is broken, not that throughput is low. Check the connectors section above before drawing conclusions.
By project
Only in the "All projects" scope. The same funnel numbers per project, plus how many items each one has in review right now, so you can see which project is dragging the aggregate.
Review queue health
How the review queue is holding up:
| In review now | Waiting for a person. |
| Oldest waiting | How long the longest-waiting item has been there. |
| At risk | Will breach its service level soon. |
| Breached SLA | Already past it. |
| Assigned / Unassigned | Whether anyone owns the work. |
Anything in Breached SLA is already late. A rising Oldest waiting combined with a high Unassigned count means nobody is working the queue, which is a staffing answer rather than a system one.
Team pace
Throughput over the last rolling hour: items per hour, and the average and median time an item spends in review. Below that, how many items each reviewer decided in that hour.
A median much lower than the average means most reviews are quick and a few are getting stuck.
Forecast
Queue depth divided by current throughput, projected forward to when the queue would clear at today's pace.
A projection of Unknown while the queue is not empty is a meaningful signal in itself: nothing cleared review in the last hour, so review has stalled. That is different from an empty queue, which also shows no projection.
In-flight reviews
Who is reviewing what at this moment, how long each item has been waiting, and how long it has been locked by its reviewer. Observe opens the transaction read-only so a supervisor can look without taking it over.
This section needs the wider monitoring permission and is available in single-project scope only.
Memory learning
Whether the project is still learning from the work your team reviews, and if not, why not. Full background in Memory.
The row shows:
- Learning or Paused, plus who paused it and when.
- When a sample was last captured.
- A breakdown of the last seven days: of the transactions that completed, how many were captured and, for the rest, the reason each was skipped.
That breakdown is the point of the section. Memory can sit empty for weeks with nothing anywhere reporting an error, and the reasons are not equally serious:
| Reason | What it means |
|---|---|
| Captured | Working. |
| Paused by operator | Deliberately stopped. Not a fault. |
| Accumulation turned off / Document examples disabled | Switched off in the published configuration. Change it in Memory settings and publish. |
| Reviewer not permitted | The person who approved the transaction lacks the "System can learn from user" permission, so their work was discarded. This is a permissions fix in Team → Roles, and it is by far the most common cause of empty memory. |
| No human reviewer | The transaction completed without anyone approving it, typically an unattended or API submission. Expected for those flows, not a fault. |
| Already captured | A re-run of something already learned. Normal. |
The first three reasons that need a human are highlighted, with the fix named underneath. Pause and Resume are available to anyone with the "Pause and resume memory learning" permission and need no publish. Note that Resume returns the project to its published configuration rather than turning learning on; if the published settings have it switched off, resuming will not start it.
In the "All projects" scope this section shows one row per project, with a count of how many need attention.
Permissions
| Capability | Permission | Built-in roles |
|---|---|---|
| Open Monitoring and see the funnel, queue health, pace and forecast for a project | View own monitoring, or the team-wide one below | Everyone, including Reviewer and Submitter |
| See in-flight reviews, and use the "All projects" scope | View all monitoring | Admin, Designer, Supervisor |
| See the import connectors section | View connectors | Admin, Designer, Supervisor |
| Pause, resume, or retry a connector | Control connectors | Admin, Designer, Supervisor |
| See the memory learning section | View memory learning status | Admin, Designer, Supervisor |
| Pause and resume memory learning | Pause and resume memory learning | Admin, Designer, Supervisor |
Sections you do not have permission for are not shown at all, so the page shape differs by role. In the "All projects" scope, only the projects you are allowed to see are included, in every section.
Ask the assistant
The in-app assistant reads the same data and can triage for you:
- "Is everything running normally?"
- "Why is nothing being imported?"
- "Which project is behind on review?"
- "Is this project still learning into memory?"
It can also act: pausing a misbehaving connector, assigning a stuck transaction to a reviewer, raising an item's priority, or pausing memory learning. It will ask you to confirm before anything that touches production.