Skip to content

Conversation

@m4dcoder
Copy link
Contributor

@m4dcoder m4dcoder commented Jul 8, 2019

Allow the workflow execution cancelation to proceed even if the workflow execution is not found or completed otherwise the method will raise an exception and the workflow execution will be stuck with a canceling status. Fixes #4735

Allow the workflow execution cancelation to proceed even if the workflow execution is not found or completed otherwise the method will raise an exception and the workflow execution will be stuck with a canceling status.
@m4dcoder m4dcoder requested a review from jinpingh July 8, 2019 23:59
@m4dcoder m4dcoder self-assigned this Jul 9, 2019
@m4dcoder m4dcoder added this to the 3.2.0 milestone Jul 9, 2019
Copy link
Contributor

@jinpingh jinpingh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should

Instead of rethrowing the exception, capture and log the error and traceback, and return the error in the result. Then let the cancelation continue to process children and determine final status. If the exception is rethrown, the workflow execution will be stuck in a canceling status. Add unit test to cover this scenario.
@m4dcoder m4dcoder force-pushed the fix-orquesta-cancel branch from f764c58 to c9c2b3c Compare July 9, 2019 07:09
@m4dcoder m4dcoder merged commit fa74d38 into master Jul 9, 2019
@m4dcoder m4dcoder deleted the fix-orquesta-cancel branch July 9, 2019 15:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Orquesta workflow execution is stuck with canceling status

3 participants