First safe session
9. First-response troubleshooting
Install Avellio, run a first audit, review findings, fix safely, and verify the result.
| Problem | What to do |
|---|---|
| Avellio is missing from Scripts | Reveal the active user scripts folder, reinstall both files, and reopen the Scripts panel. |
| Engine core disconnected | Reinstall the matched Loader + Engine package; do not rename or mix releases. |
| Avellio refuses the active document | Close the palette, activate the intended document, and relaunch the Loader. |
| Fixes asks for an audit | Run a complete Typography Audit, not only Execute Analytics or Live Mode. |
| Apply All Safe Fixes is disabled | The plan may be stale, contain no safe candidates, or have failed a guard. Read the Fix Plan and rerun the audit. |
| Analysis is slow | Reduce scope, disable Rivers, avoid Legacy Overlays, or choose a narrower profile. |
| Report is outdated | Run a full audit immediately before export. |
| Diagnostic colors remain | Use Erase Highlights, inspect conditions/layers, and accept cleanup when closing Avellio. |
| License needs validation | Connect to the internet and check the system date, firewall, proxy, and KEY status. |
Use Health in the Typography context for production diagnostics. Health checks the build, host, modules, license interface, support directory, action transactions, and palette state.
Release sourceThis page was generated from the Markdown companion of the verified distribution PDF.