Skip to main content
Open Administration → Keys and confirm the machine key is active and has events:add. Then open Observe → Events, widen the time range, and clear environment and agent filters. If events exist, search the session ID and then check Observe → Sessions for grouping. If no events exist, diagnose the Failproof daemon from the CLI.The live Events stream with its primary filters visible and recent agent events arriving.
Clear filters in Observe → Events and search the exact SDK session ID. If nothing appears, inspect the SDK spool and Failproof daemon on the source machine.
Open Admin → enforcement, select the machine, and compare its assigned, reported, and previous versions. Confirm the deployment scope includes the machine and its key has policies:pull. Ingest can work even when policy delivery does not.
Open Admin → enforcement and inspect the machine’s last-seen time and reported version. If the machine is stale, treat this as a local daemon problem. Do not weaken the deployed policy solely to bypass an unavailable daemon.
For a Cloud-authored policy, open Admin → policy editor, select the draft, and review validation errors before publishing. For a local policy, use the CLI to validate it, then open Observe → policy after a test action to confirm decisions arrive.
Open Analyze → audits, select the run, and check whether model analysis ran. Then compare its scope and window with Observe → sessions and open representative traces from that population.A zero result is meaningful only when analysis ran successfully. If analysis was skipped or failed, the run produces no findings and keeps the unanalysed window open for a future successful run. If model analysis is disabled, the audit also produces no findings because the deterministic credential and PII scan records statistics but no longer raises findings.The audit form where environment, agent, cadence, and sweep window define the session population.
Open a completed session and check whether a manual evaluation succeeds. Hosted Cloud currently has no evaluator endpoint control in the dashboard; the server operator must configure it.
Use the organization switcher and confirm the expected slug and permissions before comparing results with the CLI.
Open Observe → policy, preserve the decision and linked session, and identify the false-positive condition. Then open Admin → enforcement and roll the affected machines back to the prior version. Create a narrower version in Policy editor, test it on a small scope, and expand only after valid work succeeds.
When contacting support, include the CLI version, harness, environment, relevant session or deployment ID, and the output of failproofai config --status with secrets removed.