The simulation currently does not properly handle implicit starts (i.e. nodes in a scope without incoming sequence flows). This leads to surprises as users try it out against more complex diagrams:
See that start triggered on start event does not spawn a token on task
Expected Behavior
[ ] Implicit starts are recognized, and can be used to spawn a token (takes precedence over pause points) if, and only if there exists no explicit starts
[ ] Tokens are always spawned on all implicit starts, once a process starts
Environment
Host (Browser/Node version), if applicable: [e.g. MS Edge 18, Chrome 69, Node 10 LTS]
Describe the Bug
The simulation currently does not properly handle implicit starts (i.e. nodes in a scope without incoming sequence flows). This leads to surprises as users try it out against more complex diagrams:
Steps to Reproduce
Expected Behavior
Environment
Surfaced in this conversation