Skip to main content
The playground is a simulation that runs in your browser. It shows how Yukta moves a workflow through its nodes, and no server is contacted. Pick a preset, or edit the JSON directly. Click a node and then another node to connect them, and use Run or Step to watch the nodes change status. Shift-click a node, or use its Fail button in the table, to make it fail and see where the run goes next.

​
How the simulation differs from a real run

The playground teaches the shape of a run. It is not a test of your workflow, and a green run here does not mean the real server will accept or complete it.
The simulation leaves out the parts of a run that depend on a live server and real data:
  • No plugin work. Nodes do not call models, APIs or databases. Each node simply finishes, or fails if you mark it.
  • No retries, timeouts or limits. A node marked to fail fails at once. In a real workflow, retry, time limits and failure budgets apply first.
  • No messages or delivery modes. A node runs once per step. Real nodes handle streams of messages, with buffering and back-pressure between them.
  • No approval waits. A WAIT_FOR_SIGNAL node finishes straight away. A real one holds until a signal arrives.
  • No persistence. Nothing is stored, and a reload starts from the preset again.
  • A simplified join rule. A node waits for all of its active inputs. If one parent fails, the node ends UPSTREAM_FAILED unless you set engine.trigger to ALL_DONE or ONE_SUCCESS in its config.
  • Simplified routing. The simulation follows an error edge when its source node fails, whether or not the node sets onError to ROUTE. Ports such as invalid stay quiet unless their node fails, because the simulation cannot judge a message.
A failure that is routed to an error edge shows the failing node as FAILURE, the route target as running, and the nodes that only the normal path would reach as UPSTREAM_FAILED. Nodes that the run never needed stay PENDING and are reported as not reached.
Ready for the real thing? Read Executions, Failure handling and Delivery and back-pressure to see what the simulation leaves out, then follow the Quickstart to run a workflow on your own server.