Diagnostic sequence
Record the full warning, installed release and last successful action. Then select the failure branch. The warning alone does not prove that low capacity caused this instance.
| Observation or task | Action and evidence |
|---|---|
| Application will not open or closes immediately | The startup article associates this symptom with insufficient local disk space. Ask the administrator to check the installation/system drive roles relevant to this workstation. |
| Export fails after the application opened | The export article discusses insufficient space on the export destination. Confirm the selected destination and have its capacity checked. |
| Neither description matches | Preserve the exact warning and phase for provider support; do not force either diagnosis. |
Safe storage checks and retry
Use drive roles rather than patient-bearing paths in the worksheet. Record observed free capacity and time, without inventing a universal gigabyte requirement. An authorized administrator can decide what unrelated files may be moved or removed under the lab's storage policy.
Do not delete orders, databases, configuration or project files to clear space. Where the export source article's alternative destination is applicable and authorized, retry to an approved destination with available capacity. Keep an unsuccessful export separate from the verified delivery package.
Worked phase comparison
Hypothetical workstation A closes during startup; its export destination has ample capacity. That observation does not clear the local startup storage question. Workstation B opens normally but export to destination D fails; check D's capacity and access context rather than assuming A's startup problem applies.
What counts as recovery
For startup, confirm the application opens and the intended work is accessible without relying on an uncertain saved state. For export, verify the regenerated files and roles against the manifest before delivery. If the same error persists after authorized maintenance, send the provider the warning, release, phase, capacity observations and retry result.
Limitations and Louie validation
Louie validation pending — unverified locally. Louie/provider must reproduce the applicable error on the installed release, confirm affected drive roles, permitted storage maintenance and a verified retry. No fixed free-space threshold or guaranteed cause is established.
Use internal references in the blank worksheet. Examples are hypothetical; applicable instructions and responsible approvals govern real work.
Source notes
Official sources checked October 6, 2026. Scope and dates below; installed applicability remains unverified. Worked examples and worksheets are original.
Prepared by Pristine Dental Design · October 6, 2026.