Advanced Workflow Validation

1. Floating Nodes & Unreachable Paths

Building complex visual workflows often leads to components becoming accidentally detached from the primary execution thread. The nLink engine proactively mitigates this logic gap.

• The "Orphan" Check
  Except for Triggers (which initiate the flow), every Action or Logic node is expected to receive an incoming datastream connection. If you drag an HTTP Request Node onto the canvas but fail to connect an incoming data wire, the node becomes mathematically "Floating".
• Why It Matters
  A Floating node is unreachable. The execution engine works linearly from the Trigger. If a node is unconnected, it will never execute. The nLink studio identifies this in real-time, placing a `[⚠️] Warning` badge intuitively on the node canvas notifying you immediately that this component is orphaned.

2. Advanced Fault Tolerance (Swallowing Errors)

Network requests fail constantly (404s, 500s). By default, if a node fails via external timeout or fatal error, nLink forcefully terminates the entire workflow execution stream and throws a critical system alert.

However, experienced engineers often want to logically "catch" these errors to route fallback mechanisms, utilizing the Continue On Fail toggle.

• Opening the Error Port
  When you enable `continueOnFail` natively inside a node's configuration, nLink overrides its default crash behavior. Instead, it unlocks a hidden, secondary Error Output Port on the visual canvas specifically dedicated to fielding caught exceptions.
• Dangling Error Port Protection
  Enabling `continueOnFail` but forgetting to attach a fallback node to the new Error Port creates a "Dangling Catch" scenario causing the workflow to swallow the error silently and halt abruptly. If nLink detects that your Error Port is completely unconnected, it forcefully triggers a real-time reactive Warning Toast, preventing silent execution death.

Best Practice: Always attach a notification node (like Slack, Gmail, or a Database logger) explicitly to the Error Port when continueOnFail is toggled to actively monitor API outages.

3. The Architecture Publish Gatekeeper

nLink's compilation engine guarantees system-wide validity prior to pushing a local draft logic matrix natively into a production server runtime state.

Workflow Validation Sequence:
==========================================
1. Evaluate Graph Nodes Count > 0
2. Detect at least One Mandatory Trigger Node [Schedule, Webhook, Zalo OA]
3. Evaluate Input/Output Integrity Checksum

STATUS: [PASSED] -> Granted Publish Rights

Trigger Nodes Are Mandatory: nLink completely disallows the compilation block and refuses `Publish` commands if the canvas lacks a valid, recognized Trigger Node. A massive graph of highly complex Actions is fundamentally inert if the engine does not possess an explicit HTTP listener or Temporal Cron job to initially spark the execution stream.