Diagnostics
Computtite exposes several diagnostic tools for understanding the health of your workspace and application state. These are primarily useful for Admins and Owners troubleshooting issues, or for technical users who want to understand what the app is doing under the hood.
Workspace Health Panel
The workspace dashboard shows a live health overview with signals grouped by severity. These signals are computed from the current database state every time the dashboard loads:
- Critical signals: Expired software licenses (past their
expiresAtdate), seat overages (more seats used than total allocated), and assets that have been in a maintenance status for an unexpectedly long time. - Warning signals: Licenses expiring within the next 30 days, assets with no employee assignment for an extended period, employees who have no assets assigned to them, and assets missing key fields (e.g., no serial number on a laptop).
- Info signals: Assets without photos, suggestions for optional data completeness.
Each signal shows a count and a breakdown by asset type. Clicking a signal navigates you to the relevant filtered asset list so you can act on the issue directly.
Workspace Statistics
The dashboard also shows a summary of current workspace statistics:
- Total assets registered
- Assets currently assigned vs. unassigned
- Assets currently in a maintenance status
- Active assignments (assets checked out to an employee)
- Licenses expiring within 30 days
Workspace Integrity Check
Computtite automatically checks the integrity of your workspace file on every startup. If a problem is detected (caused by disk errors, abrupt power loss, or filesystem issues), the app enters safe recovery mode: the workspace is locked for editing to prevent making things worse, and the import tool is presented so you can restore from a backup.
You can also run the check manually at any time from Settings → Storage → Check database integrity.
Sync Log
In cloud mode, the sync log (Settings → Sync → View sync log) shows the history of sync operations: what was pushed, what was pulled, any conflicts that occurred, and any operations that failed. Each entry includes a timestamp, the table and record affected, and the operation result. This is the primary diagnostic tool for understanding why specific changes did or didn't propagate.
Application Version and Build Info
The currently running version, build date, and platform details are shown in Settings → About. This information is useful when reporting bugs — always include the version number and platform in a bug report.