Troubleshooting
Open Chat → Diagnostics first. It checks tables, public files, PHP extensions, agents and dispatch age; it cannot prove external provider delivery.
| Symptom | Check |
|---|---|
| Widget hidden | Correct site enabled, server working hours, open authorized manager workspace; allow up to 30 seconds; clear composite HTML cache if needed |
| Widget says you are an operator | Expected self-chat prevention; use another visitor profile |
| Disabling widget blocks history/PWA | Update to 0.4.20+ including public files, then check login/site/department rights |
| Closed row remains | Expected under All; under Open, update to 0.4.19+ and refresh public assets |
| PWA starts at All | Update workspace files to 0.4.19+ and reopen the application |
| PWA installation stalls | Trusted HTTPS, separate workspace, regular browser window; 0.4.22 restores stalled buttons; use manual Yandex installation |
| No system notification | Browser/OS permission, completed subscription, login, recurring server runner; test a new unread message |
| No sound | Nonzero volume, unmuted tab, initial user gesture; read messages should no longer remind |
| Update seems ineffective | Update modules and public js/tools/admin files; check a second local/modules copy, composite cache and OPcache |
| Link blocked | Without a key, confirm navigation; with VirusTotal, wait for a valid result; errors/threats block it |
Report module/browser/OS versions, workspace URL, exact error, action and server time, and whether you used administration or standalone PWA. Do not send passwords, cookies, API keys or private URL parameters. Redact personal data from screenshots.