Open ben-mays opened 8 years ago
Additionally, the workflow executor does not log the failure anywhere and simply blackholes failures in the signal-induced DecisionTasks.
:+1:
:pray:
+1
@ben-mays Can you provide the code you are using to run the worker/activity_worker/starter? I was getting a similar issue where I'd get DecisionTaskStarted
but never DecisionTaskCompleted
, and the workflow would apparently blackhole the error and timeout. Bumping to 3.1.0(the newest release, which for some reason is not in the gemfile for the samples repo) allowed it to properly raise the exception and let me see my error, and after adding a value to start_execution allowed it to go through correctly(I still get an error, but that's due to amount
not being defined in the code snippet given)
@mjsteger sorry, we're actively moving functionality off of SWF as a result of this and numerous other issues that manifested themselves- long polling causing tasks to be scheduled on dead sockets, the decision/activity context not being set, a memory leak that won't go away. I'll leave the issue open for others that may have the same issue.
@ben-mays Do you have any literature you've written about these issues? Did you happen to use the JVM Flow framework as well or are these experiences solely based on the ruby version? Can you speak to what you've switched to (assuming custom-grown workflow management on-top of a message bus)?
Running the sample code given with a reference to the
decision_context
causes theDecisionTask
to fail. The execution history showsDecisionTaskScheduled
,DecisionTaskStarted
but neverDecisionTaskCompleted
. Eventually the workflow will timeout. The cause is thedecision_context
resolving tonil
.Here is the modified code to reproduce: