Skip to content

[Wf-Diagnostics] retrieve workflow execution history within issue identification activity#6607

Merged
sankari165 merged 1 commit intocadence-workflow:masterfrom
sankari165:CDNC-10295
Jan 10, 2025
Merged

[Wf-Diagnostics] retrieve workflow execution history within issue identification activity#6607
sankari165 merged 1 commit intocadence-workflow:masterfrom
sankari165:CDNC-10295

Conversation

@sankari165
Copy link
Member

What changed?
workflow execution history was retrieved in a separate activity and now is moved under the issue identification activity in diagnostics workflow

Why?
for long running workflows, the result will be too large to be passed within activities

How did you test it?
unit tests

Potential risks

Release notes

Documentation Changes

Domain string
}

func (w *dw) retrieveExecutionHistory(ctx context.Context, info retrieveExecutionHistoryInputParams) (*types.GetWorkflowExecutionHistoryResponse, error) {
Copy link
Contributor

Choose a reason for hiding this comment

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

The downside of this change is that you will have to download history multiple times for all diagnostics. If performance considerations arise, we might need to work on an external storage option to pull it from the DB once and then only download it from the storage (which should be faster).

Copy link
Member Author

Choose a reason for hiding this comment

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

All issue checks are done after the history retrieval so its ok with the current req but I do agree that if we have to share it amongst other modules we need ext storage

@sankari165 sankari165 merged commit e047ef3 into cadence-workflow:master Jan 10, 2025
23 checks passed
@sankari165 sankari165 deleted the CDNC-10295 branch January 10, 2025 15:06
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

Comments