Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

continue as new for retry should have reason #902

Closed
yiminc-zz opened this issue Jun 27, 2018 · 0 comments
Closed

continue as new for retry should have reason #902

yiminc-zz opened this issue Jun 27, 2018 · 0 comments
Labels
serviceability Improvements to servicing of Cadence Server
Milestone

Comments

@yiminc-zz
Copy link

When workflow is scheduled with retry policy, and when the workflow failed server would do continue as new instead of fail the workflow and a new workflow execution will be started. The last event of the failed workflow execution will be ContinueAsNew event. When user look at the event they have no clue what caused the failure. We should add a FailedReason/FailedDetails to the ContinueAsNew event so when people look at the event it knows why it is doing continue as new.

@dmetzgar dmetzgar added the serviceability Improvements to servicing of Cadence Server label Sep 12, 2018
@dmetzgar dmetzgar added this to the Quality milestone Sep 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
serviceability Improvements to servicing of Cadence Server
Projects
None yet
Development

No branches or pull requests

3 participants