Operate · Common questions
Troubleshooting Phigon
Start with three things: connection, consent, and coverage. Those signals explain most unexpected workspace states.
A machine appears offline
Confirm that the supervised machine is powered on, connected, and running its approved observer. Check whether its last report is merely stale or fully unavailable.
Remember: a disconnected observer does not prove an agent is inactive.
Activity is marked limited
Open the evidence details and identify which expected source is unavailable. The remaining source may still provide useful context, but it supports a narrower claim.
Restore the missing coverage before treating the activity as fully supported.
Evidence sources conflict
Review each source independently, including its timestamp, process identity, and coverage window. Do not resolve a conflict using a PID alone.
If the disagreement cannot be explained, leave attribution unresolved.
Consent is missing or revoked
Ask the machine owner to review the current request on their machine. Do not bypass or silently restore a revoked scope.
Collection can resume only after valid approval.
Expected history is absent
Check the selected:
- Time window
- Machine
- Agent filter
- Retention boundary
- Collection scope that applied at the time
An absent record is not proof that no activity happened.
Search does not find a page
Try a short operational term such as consent, pairing, offline, evidence, coverage, or support. You can open documentation search with / or Command/Ctrl + K.
Contacting support
Include the machine label, approximate time, visible evidence state, and safe steps you already tried.
Never send credentials, secrets, prompt contents, terminal contents, or personal data by email.