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

[Wf-Diagnostics] add retry policy validation to diagnostics #6529

Merged
merged 1 commit into from
Nov 29, 2024

Conversation

sankari165
Copy link
Member

What changed?
Retry policy validation added to retry invariant in diagnostics

Why?
Customers have invalid policies running in production and hence cannot be stopped via server side validation but they still cause a lot of questions in support channel and hence it is better to convey via diagnostics

How did you test it?
unit tests

Potential risks

Release notes

Documentation Changes

@@ -85,9 +109,22 @@ func fetchStartedEvent(events []*types.HistoryEvent) *types.WorkflowExecutionSta
return nil
}

func checkRetryPolicy(policy *types.RetryPolicy) IssueType {
if policy == nil {
return ""
Copy link
Contributor

Choose a reason for hiding this comment

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

Unsure if it is an issue - but missing retry policies for activities could be a good sign of issues - due to Cadence not being able to retry it on schedule to start/panic any timeout.

Copy link
Member Author

Choose a reason for hiding this comment

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

yeah its. a grey area. I added it is an issue when an activity has heartbeating configured and no retry policy but havent raised missing retry policy by itself as an issue since I thought it would show up on a lot of workflows and might get ignored out of annoyance

@sankari165 sankari165 merged commit eacb093 into cadence-workflow:master Nov 29, 2024
17 checks passed
@sankari165 sankari165 deleted the CDNC-11704 branch November 29, 2024 14:14
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.

2 participants