## Summary of Current Issues
-
Canvas Bloat and Graph Reliability Limits (~1,700 Nodes)
-
The Problem: Replicating condition blocks, premium captures, orders, exit checks, and alerts across numerous individual branches has pushed your canvas to roughly 1,700 nodes.
-
Impact: The system frequently returns “Unable to read current canvas” or forces server rejections because parsing, validating, and compiling a massive deeply-nested graph exceeds real-time payload thresholds.
-
Verification: Canvas rendering stability degrades exponentially past a few hundred active operational nodes, causing server-side time-outs or silent rejections.
-
-
Single-Input Node Constraints
-
The Problem: Standard nodes within the flow architecture enforce a strict single-input or isolated-branch model. When trying to merge multiple validation paths or consolidate branch exits without duplicating logic, you are forced to clone blocks repeatedly, causing the branch count to explode.
-
Impact: Inability to scale complex multi-leg/multi-condition strategies organically without hitting architectural design blocks.
-
-
Incomplete Stage/Branch Deployment
-
The Problem: Critical execution blocks—specifically segments like
ANY94,ANY95,ANY64toANY71, and the entire Stage 4 setup before 3:20 PM—remain unbuilt or stripped down because the server rejects inline premium checks added directly into trigger/exit blocks. -
Impact: The automated strategy remains incomplete, halting deployment via the primary Start execution button.
-
## Evaluation of we Proposed Solution (“Any Node” Multiple Inputs)
we suggest to allow ANY nodes (or a dedicated merger/junction block) to accept multiple incoming input paths is architecturally sound and standard practice in node-based workflow engines:
-
Why it helps: Allowing an
ANYcondition or a merge block to aggregate multiple incoming true/false states or exit triggers prevents redundant block duplication. Instead of creating separate exit handlers for every single branch permutation, multiple branches can flow into a single unifiedANYevaluation node. -
The tradeoff: While this drastically reduces canvas clutter and tree depth, platform-side execution engines must still handle concurrent evaluation queues. If FYERS Automate natively implements multi-input fan-in capabilities for
ANY/ORgates, it will significantly reduce graph size and bypass current server validation errors.