Troubleshooting

Troubleshooting is organized by symptom rather than component internals. Each page must identify observable signals, safe diagnostic steps, likely causes, recovery actions, and escalation evidence.

Choose the symptom area:

• Installation
• Login and access
• Notification delivery
• Incident processing
• Inbound integrations
• Status pages
• Workers
• Scheduler
• Database and PgBouncer
• Kubernetes
• Upgrades and migrations