Statuses and what they mean
A status in the Control room is always an icon and a word, never colour alone, so it reads the same for everyone and in
every theme. This page lists them by where you meet them. When a status needs action, the page that shows it says what
to do, and Home's Needs attention usually lists it too.
Keys
| Status |
Meaning |
| ✓ Active |
The key can call the models it's allowed |
| ! Suspended |
Stopped for now; resuming brings it back. The key says why: suspended by hand, unused for the organisation's dormant-key period, its person disabled, its agent suspended, a budget covering it reached, … |
| ! Expired |
It passed its expiry date; Vidai revokes a key the moment it expires |
| ✕ Revoked |
Stopped for good |
Whether the gateway has the key's latest settings:
| Status |
Meaning |
| ✓ On the gateway |
The gateway has it as Vidai does |
| i Reaching the gateway |
A change is on its way, usually within seconds |
| ! Differs on the gateway |
Out of step; Home lists it |
| ✕ Not on the gateway |
The gateway doesn't have it |
Calls (Request logs)
| Status |
Meaning |
| Served |
A model answered |
| Refused |
The gateway turned the call down, for example refused by a policy, a budget, a rate limit or Stop AI traffic. The call says what refused it, in words |
| Failed |
Something went wrong at the gateway, at the provider, or on the caller's side |
Beside the outcome, a second mark says what guardrails did: Blocked, Masked, Pseudonymised,
Redirected or Logged. Nothing is added when guardrails passed the call. A call can also be partly checked:
a check it needed couldn't run, and the guardrails setting let it through.
Policies
| Status |
Meaning |
| Draft |
Nothing is applied |
| Observing |
Guardrail parts log what they find without acting; other parts aren't applied yet |
| Enforcing |
Every part is in force |
| Paused |
Every part is lifted until someone resumes it; it stays on Home while paused |
Coverage of a regulation Enterprise
| Status |
Meaning |
| Enforced |
Every key in scope has it in force |
| Observed only |
Watched and logged, but some keys only observe |
| Partly |
Some keys have it and some don't |
| Not checked |
It needs VidaiGuard. Where VidaiGuard isn't set up, this is calm: pattern checks still act, and it starts once VidaiGuard is set up. Where it's set up but switched off or not answering, it's a warning |
| Nothing in place |
Nothing in scope provides it yet |
| Your organisation's process |
The product doesn't cover it; always listed, last |
A control covered by a pack whose VidaiGuard checks don't run now also says Partly by patterns, with why.
Evidence
| Status |
Meaning |
| ✓ Verified |
Every record checked is as it was sealed |
| ! Partly verified |
Part of the check couldn't be done, with why: the gateway didn't answer or isn't recording, its records couldn't be read, its key isn't confirmed yet, … |
| ✕ Failed |
Something changed or is missing. Don't hand evidence over before you know why |
| Never verified |
No check has run yet |
Budgets
| Status |
Meaning |
| ✓ Within budget |
Spend is under every threshold |
| ! Past a threshold |
Spend passed one of its warning thresholds |
| ✕ Reached |
The limit is reached; the budget acts as set (warn, stop calls, or switch to a cheaper model) |
Billing periods
| Status |
Meaning |
| Open |
Costs can still change |
| Partly locked |
Some days are locked |
| Final |
Locked: nothing changes these days' costs |
Approvals
Waiting, Approved, Refused, Cancelled, Expired, or Closed (it no longer applies, for example
another admin decided it first).
Rate card
| Status |
Meaning |
| Not connected |
No rate card yet: models can't be priced from it |
| Not synced yet |
Connected, waiting for the first sync |
| ✓ Up to date |
Synced on time |
| ! Out of date |
No sync for longer than expected; prices on file still apply |
| ✕ Failing |
The last sync failed; prices on file still apply |
| ! Stuck |
A sync has waited more than half an hour to start: check Status |
| Disconnected |
Syncing stopped; prices on file keep pricing calls |
Stop AI traffic and gateway nodes
| Status |
Meaning |
| Off |
Traffic flows |
| Engaged |
Every AI call is refused until an organisation admin releases it |
| Not taken everywhere |
At least one gateway node disagrees; a partial stop never reads as a full one |
| Serving calls / Refusing calls |
What each node is doing |
| Still serving calls / Still refusing calls |
The node hasn't taken the last change yet; Vidai keeps trying |
| Not answering |
The node didn't answer |
VidaiGuard Enterprise
On Enterprise, VidaiGuard is set up or not set up; both are normal, and guardrails are complete on pattern checks
either way.
| Where |
Statuses |
| Settings › VidaiGuard, Guardrails › Overview |
i Not set up (pattern checks act on their own; it says how to set it up), Answering, Not answering, Checks off, Not known yet |
| The VidaiGuard tile on Dashboard › Compliance |
i Not set up, Working, Not answering, Checks off, Not known yet |
| A pack |
Patterns only, VidaiGuard not set up, VidaiGuard checks off, VidaiGuard on, Partly by patterns, Patterns only: no VidaiGuard model, VidaiGuard unavailable: patterns only, Refused while VidaiGuard is unavailable: see Add a pack to a level |
System › Status
| Part |
Statuses |
| Summary |
Everything is working, Some parts need attention, or a line saying Vidai can't reach its own database |
| Gateway |
Working, Answering, but not healthy, Not answering; its version Supported or Too old |
| Usage and request logs |
Recording, Partly recording, Not recording |
| Gateway instances |
Up to date, Picking up the latest change, Not heard from just now |
| Pattern rules |
Enforcing, Partly enforcing, Not enforcing |
| VidaiGuard Enterprise |
Connected, Connecting, Down, Switched off, Not available, Not set up |
| Database |
Connected or Not reachable; its version Up to date or Needs updating |
When the gateway isn't answering, guardrails show Unknown: they're never shown as working when they can't be
checked.
Email, events and BI push
| Where |
Statuses |
| Email log |
Sent, Waiting to send, Failed (with the last problem, in words) |
| Event destinations |
Sending, Paused, Failing (with how many sends failed in a row, and the next try) |
| Event deliveries |
Delivered, Failed |
| BI schedules |
Working, Paused, Failed a number of times since it last worked |
| BI deliveries |
Delivered, Failed |
Licence
| Where |
Statuses |
| Features |
Included, Needs a licence, Needs the Enterprise edition |
| Limits |
Nearly at the limit (from 90%), Limit reached, or no limit |