Error aggregation
The error view groups incidents by dimensions you select:- Error type or canonical code (for example connector timeout, permission denied)
- Pipeline and environment
- Node or connector family
- Time window
Error types
Planasonix classifies errors at multiple layers:| Layer | Examples |
|---|---|
| Orchestration | Schedule skipped, concurrency cap, invalid parameter |
| Connectivity | DNS failure, TLS handshake, proxy reset |
| Authentication | Expired OAuth, warehouse user locked, IAM deny |
| Data | Type coercion, constraint violation, missing partition |
| Resource | OOM, disk spill, slot unavailable |
Some connectors wrap vendor codes; the UI maps them to stable categories for filtering even when the raw message changes between driver versions.
Stack traces
When the engine captures them, failed nodes include stack traces or exception chains in the error panel. Use traces to distinguish:- Your transform code bugs
- Platform defects (open a support case with run id)
- Upstream instability masked as generic socket errors
From error to fix
Open the sample run
Use the latest occurrence link to jump into run history with the failing node pre-selected.
Compare with last success
Diff parameters, row counts, and warehouse warehouse from the previous green run.
Check dependencies
Verify connections, secrets rotation, and schema migrations in the source system.
Troubleshooting guides
Use these docs when errors span multiple systems or you need platform-specific depth:Diagnostics
System health, tracing, and support data collection.
Dead letter queue
Recover and replay failed events in streaming paths.
Alerts
Route failures to on-call before users notice dashboards.
AI Copilot chat
Ask questions grounded in your workspace context where enabled.
Related topics
Run history
Full execution list, durations, and node-level logs.