pmohan6
commented
10 years ago We definitely need to improve logging here. This error usually indicates that the state machine that was supposed to consume a symbol doesn't exist anymore.
Did you see this with the latest version of ruby flow?
We have seen this in a few cases - 1) Do you have a multi threaded model by any chance? Ruby flow is not tested to be thread safe. 2) Do you use timers? We recently fixed a bug in our Timer state machine that was causing this error. 3) Related to 2, do you schedule more than 100 decisions at once? In such a case, ruby flow will break the decisions in chunks of 99 + 1 (timer) and schedule them separately.
Can you share with us a small repro if you notice this with the latest version of ruby flow?
Tsquare
I'm seeing intermittent errors like this in the AWS-Flow-WorkflowTaskPoller log file: I, [2014-07-08T21:43:39.541507 #6052] INFO -- : Got decision task ... E, [2014-07-08T21:43:44.207649 #6052] ERROR -- : Error in the poller, NoMethodError, undefined method `consume' for nil:NilClass
For the same flow with the same parameters, etc, we sometimes get this error with the result that decision tasks time out and the flow never completes, and sometimes everything completes normally.