Diagnosly
Register
Product How it works Personality Pricing Docs Sign in Register
Browse documentation
Personal
Getting started
What is Diagnosly Personal?Signing inInstalling the appYour first diagnosisA tour of the app
Using Diagnosly
Running a diagnosisDiagnosis historyFollow-upsWhat it can change, and how you approve itBackups and restore pointsApp updates
Credits and billing
How credits workSpending limits and checkpointsTopping up
Privacy and security
Privacy basics (PII scrubber)Your data and deleting your account
Help
TroubleshootingFrequently asked questions
Enterprise

For IT teams managing many PCs. Not needed for Diagnosly Personal.Learn more

Set up your fleet
Fleet agent installSetting up your first fleet
Fleet management
Fleet overviewFavouriting devicesBulk actionsRunning checksCommand audit trailFleet troubleshooting & alerts
Security and access
Role-based access control
Integrations
SSO with OktaSSO with Azure AD / Entra IDSMTP / email

Fleet troubleshooting & alerts

Fleet failure modes and fixes, agent not appearing, command hanging, AI diagnose failing, alerts and notifications.

Agent installed but doesn't appear in Fleet

Most common causes:

  1. Service didn't start. Check Get-Service diagnosly-agent, should be Running. If Stopped, run Start-Service diagnosly-agent as admin.
  2. Token already used. Install tokens are single-use. Generate a new one and re-run register.
  3. Network blocked. The agent must reach the gateway over HTTPS. Check Windows Firewall + corporate proxy.
  4. Agent on the wrong tenant. If you have multiple agent.env profiles, use --profile <name> explicitly to avoid alphabetical auto-pick.

Command hangs in running forever

Either the agent crashed mid-execution, or the script blocks on user input. Background timeout job will mark it timeout after the per-type threshold (see Command audit trail). Force-cancel via the Cancel button on the command row.

AI diagnose fails with "Claude Code not found"

The agent locates an installed Claude Code automatically. If it isn't found, install Claude Code via the dashboard's Deploy AI action, that's the recommended path for production.

If diagnose fails with "API key not found", visit Settings → LLM Providers and confirm the active provider has a valid key. Demo tenants don't ship with a key, bring your own Anthropic / OpenAI / GLM key.

Notifications

The bell in the topbar shows unread notifications. Types:

alert_triggered · alert_escalated · device_offline · device_online · task_completed · task_failed · script_failed · system

Alerts are generated when device metrics exceed configured thresholds (CPU, memory, disk). Alert escalation runs every 60 s, unacknowledged alerts escalate to critical after a configurable timeout.

:::callout type="info" Heartbeat error log shows "Failed to send heartbeat: connect refused", the agent and gateway can't talk. Verify the gateway is reachable from the target machine and that no proxy/firewall is in the way. :::