Max Callstack size exceeded?

[NullVoxPopuli]

I'm not sure where to look to find this:

scheduler.js:72 Uncaught RangeError: Maximum call stack size exceeded
    at StateNode.resolveTransition (StateNode.js:888)
    at StateNode.transition (StateNode.js:824)
    at StateNode.resolveRaisedTransition (StateNode.js:831)
    at StateNode.resolveTransition (StateNode.js:954)
    at StateNode.transition (StateNode.js:824)
    at StateNode.resolveRaisedTransition (StateNode.js:831)
    at StateNode.resolveTransition (StateNode.js:954)
    at StateNode.transition (StateNode.js:824)
    at StateNode.resolveRaisedTransition (StateNode.js:831)
    at StateNode.resolveTransition (StateNode.js:954)
Scheduler.process @ scheduler.js:72
Scheduler.schedule @ scheduler.js:46
Interpreter.send @ interpreter.js:116
send @ use-machine.js:119
start @ index.js:119
09:39:22.617 

I haven't been able to reproduce in a codesandbox, so it's only happening in my app so far.
Seems to be when I transition two separate machines at the same time? idk.
If I delete the entry actions from one machine, the error doesn't occur. o.o

Super puzzled by this (for now), and if anyone has seen this before, any help would be much appreciated :D

What's baffling to me is that the stack isn't that deep 🤔

Ah, moving the transition / state machine creation into a setTimeout such as

      setTimeout(() => this.gameHost?.startGame(), 2000);

shows the full stack trace. woo!

[NullVoxPopuli]

Ah! I was mis-using always. I changed to use entry, which fixes my issue

[davidkpiano]

Yeah, we should post better warnings about this when detecting that always might be used incorrectly.