Skip to main content
When a pipeline fails, you want three answers: which node, why, and whether the data is safe to retry. Planasonix surfaces that through run history, node status, and logs. This page groups the failures operators see most often and the fastest ways to narrow them down.

​
Common errors

A single node turns red while upstream stayed green. Open node details for the exception class, SQL state, or HTTP status. Typical causes: syntax after variable substitution, missing file, forbidden API, or type coercion on null-heavy columns. Fix the node config or guard with null-safe expressions and default values.

​
Debugging with preview, node logs, and run details

1

Open the failed run

From the pipeline canvas or Runs list, select the attempt with the error badge. Note start time, environment, and parameter overrides.
2

Read node logs

Expand the failed node and load logs filtered to Error and Warn. Follow stack traces to the first caused by line—later messages are often cascading.
3

Use preview where safe

Preview samples rows through the subgraph. Use limited row counts and masked columns for PII. Preview hits the same connections as production—respect rate limits on external APIs.
4

Compare to last success

Use diff on Git commits or version history if the pipeline changed between green and red runs. Roll back one change at a time.
Some failures are transient (network blips). Use retry policies on idempotent branches instead of manual reruns for every flake.

​
Performance optimization tips

Filter and project in source queries or warehouse SQL before you move large datasets through the orchestration tier.
Too many tiny files hurts listing; too few huge files hurts parallelism. Aim for 128–512 MB compressed objects where the format allows, subject to source constraints.
Reuse broadcast or cached small lookups instead of repeating joins on every micro-batch in streaming paths.
Backpressure in streaming or orchestrated jobs shows up as growing lag before hard failures. Alert on lag early.
Capture a baseline duration after a healthy run; alert when p95 doubles—that catches regression before hard timeouts fire.

Diagnostics

Automated anomaly hints across runs.

Dead letter queue

Inspect rejected rows and poison messages.