Reference checklists
| Area | What to verify | Why it matters |
|---|---|---|
| Browser environment | Version, extensions, cache, cookies, trusted sites | Eliminates local rendering and script conflicts |
| Network path | VPN, proxy, firewall, DNS, TLS inspection | Explains blocked scripts, downloads, and redirects |
| Session stability | Idle timeout, multi-tab activity, re-auth prompts | Prevents lost work during longer workflows |
| File preparation | Filename rules, format, size, encoding, pop-ups | Reduces upload failures and silent rejections |
| Error documentation | Timestamp, screenshot, step number, affected users | Speeds up communication with official support teams |
Best practice
Keep an internal worksheet for recurring interruptions. The most useful fields are date, process name, browser version, network type, exact error text, whether a second user could reproduce the issue, and whether the problem occurred before or after an inactivity period. This prevents vague escalations and makes the official support conversation more productive.