Checks
Does this still work? Answered with pass or fail.
A Check walks one process or control the way a person would: a deal becomes an invoice, a report lands on time, a service answers at its own address. Every step must observe what it expects, on a schedule you set.
Check · every hour · Salesforce to Oracle
A closed deal becomes an invoice within 15 minutes
Opportunity OPP-58213 set to Closed Won
Quote Q-20481 approved in 2.1s
…
…
…
Remove the test deal, quote and order
WaitingWhy it failed
Oracle’s invoicing job has been paused since Tuesday’s patch
ExpectedInvoice within 15 min
ObservedNo invoice
Last passedTuesday, 18:00
Also affected37 real orders, $412k
Fix
Resume the invoicing schedule, then re-run the 37 orders
Last 14 runs
hourlyFailing for 4 hours. Nobody had noticed.
Results
Four honest answers.
Never a default green.
Every run ends in exactly one of these, and keeps the evidence that produced it.
Passed
Every step observed what it expected. The run keeps what it saw at each step.
Failed
A step did not hold. The step is named, with what it expected and what it observed instead.
Could not verify
Access was missing or the system did not answer. Reported as its own result, never counted as a pass.
Collected
The run gathered evidence without a pass or fail condition, ready for a person or a later step to judge.
How a Check runs
Steps, in order.
Cleanup always runs.
A Check is a short sequence of steps against the systems you already use. If a step fails, later steps are skipped and the reason is kept.
- 1Describe
Say what must be true
Write it in plain language. Panaptico proposes the steps, the systems they touch, and what each must observe.
- 2Review
See what it proves
Each Check states what it proves and what it cannot establish, before it ever runs.
- 3Run
On a schedule you set
Hourly, daily, or before and after a change. Read-only by default; any step that writes is marked first.
- 4Record
Every run kept
Pass or fail, the observed values, timings, and the fix. The history shows exactly when it stopped working.
When it fails
The failing step, named.
With what it saw and how to fix it.
- Expected and observed values side by side
- When it last passed, so you know how long it has been broken
- What else the same failure touches
- A specific fix, ready to hand to the system's owner
Read-only by default
Most Checks only read. Steps that create test records say so and clean up after themselves.
No silent passes
Missing access or an unreachable system is reported as could not verify, not as green.
Examples
Checks teams run.
Across IT and the business.
Works with
The rest of the platform.
One record of what's true.
Pick one thing that must work.
Know, every hour, that it does.
Start with a single process you rely on. Panaptico proposes the Check and runs it on your schedule.