Diagnose slow or broken behavior
Collect evidence before choosing a fix.
Reviewed 6 October 2026 · 2 min read
Import example project ↗Two named conversations, shared files, revisions and a preview.
Before you start
Record expected behavior, actual behavior and time. Include version, OS, device and reproduction steps.
Logs may contain private data. Share relevant excerpts and redact secrets.
Step by step
- Reproduce once and note timestamp/timezone.
- Inspect process status, app logs and relevant OS events.
- For slowness, measure operation duration and CPU, memory, disk/network activity.
- Change one likely cause and compare the same check.
Try this
Example request
Investigate slow project settings. Measure the delay and relevant requests. Identify UI, network or server time, fix the cause and repeat the measurement.
Check the result
- The diagnosis uses observed evidence.
- Before/after measures refer to the same action.
- The fix preserves authentication and data integrity.
If something goes wrong
For invisible apps, inspect window lifecycle rather than repeatedly reinstalling.
Old event-log errors may be unrelated; correlate them with the reproduced failure.
Your screen may differ by platform and version. Check availability or get help.