Operations
Read your workspace's operational record: platform status, scheduled jobs, the audit trail, run receipts and model usage.
Operations is your workspace's own operational record: system pulse, scheduled work, and a way to retrace any event end to end. It is for reading and understanding. This page explains its five tabs and where to go when you need to act.
Before you start
- Open Governance › Operations.
- Each tab tells you when your role does not allow you to read it.
- Everything on Operations reads your workspace's own data. Diagnostics of Nexa's servers are not part of it.
Know the five tabs
| Tab | What it answers |
|---|---|
| Pulse | Is the platform up? Which services are healthy or degraded right now. |
| Scheduled jobs | What runs on a schedule: what, how often, last run, status. |
| Audit trail | Who did what: every governed action of a person, an agent or the platform, in sentences. |
| Receipts | Whose time was this, and what did it cost: one line per agent turn. |
| Usage | Model and token usage for the workspace, by agent and by model. |
Chobin, the Operations Intelligence agent, is the resident of every tab. Click Ask Chobin at the top right to have the page explained. See Asking Chobin.
Check that the platform is up
Open Governance › Operations.
It opens on Pulse.
Read the banner, for example All systems operational.
Below, Platform services lists each service with its status: API gateway, Database, Knowledge index, Embeddings, Event bus and Web search. Each reads healthy, degraded, down or unreachable. The list updates every 10 seconds.
When a service shows a signal, the Ask Chobin pill carries a dot. Opening it places a diagnosis question in the chat for you to send.
See what runs on a schedule
Open the Scheduled jobs tab.
Read each row: Job, Schedule, Last run, Status and Enabled. The status reads Active, Paused, Overdue or Error.
With the permission to manage operations, the Enabled switch pauses or resumes a job, and Remove deletes it. Rows marked Read only, with a lock, cannot be changed here. Without that permission, the list is read-only.
Retrace an event
Open Audit trail to find who did what. See Audit trail.
Open the details of an entry that belongs to an agent's run, and click Open the receipt.
The receipt says how long the run took, whose time it was and what it cost. See Receipts.
From a receipt, Looking for who approved what? leads back to the audit trail, filtered on that agent.
See which agents and models used the most
Open Usage and pick Today, 7 days or 30 days. See Usage.
Where to act
Operations is for reading. To act:
- Change a routine on the Company Clock, in Focus › Schedule.
- Take a decision in Focus › Pending Actions.
- Report a platform failure in Settings › Support.
What you will see
Good to know
- The audit trail answers "who did what". Receipts answer "whose time was this, and what did it cost". The trail's rows link into the receipts.
- Nothing on Operations shows raw data, internal identifiers or the contents of your work.
- When something is wrong, quote a receipt's reference in a support ticket: support opens exactly that run.