NodeFox

Lesson 20 · Advanced

Diagnose a waiting or failed workflow

Trace the first missing prerequisite instead of rerunning the whole process.

Written guide · 3 min read · video not yet produced

See the actual editor and execution log

This original 20-second silent recording shows a contract-review network executing in the real application. It provides interface context; it is not a step-by-step recording of this lesson. The written guide below explains what to inspect.

Actual product footage · 20-second silent excerpt. A sample contract-review network runs model, code and routing steps; execution logs appear alongside the graph. This is a product demonstration, not a customer result.

Before you start

A signed-in NodeFox workspace. Use synthetic data and prepare outputs before enabling external writes.

  1. 01Find the first divergence

    Compare the intended graph with the observed execution. Identify the first step that did not receive its expected value, did not become ready, or returned an error. Later empty outputs may only be symptoms.

  2. 02Inspect inputs and controls

    Check slot numbers, required inputs, activation conditions and global names. Inspect the value’s type as well as its visible text. A value on input 2 cannot satisfy a template that reads $1.

  3. 03Separate external failures

    A provider error, permission failure, malformed API response and missing file require different remedies. Preserve the error evidence. Do not make a failed external dependency look like an ordinary empty result.

  4. 04Retest safely

    Duplicate the learning graph or use synthetic inputs. Prepare outputs locally. Before repeating any graph with an external Writer, reconcile whether the previous action happened and whether the destination supports duplicate prevention.

If the result is wrong

A full rerun can repeat side effects. Inspect the destination before using rerun as a recovery strategy.