workflow: retention policy is not retroactive#5074
Open
JoshVanL wants to merge 2 commits intodapr:v1.17from
Open
workflow: retention policy is not retroactive#5074JoshVanL wants to merge 2 commits intodapr:v1.17from
JoshVanL wants to merge 2 commits intodapr:v1.17from
Conversation
Clarify that adding or changing a retention policy does not retroactively purge workflows already in a terminal state. Include CLI examples for retroactive cleanup using `dapr workflow purge --all-older-than` and `dapr workflow list --filter-status` combined with purge. Signed-off-by: joshvanl <me@joshvanl.dev>
Contributor
There was a problem hiding this comment.
Pull request overview
Clarifies Dapr Workflow history retention behavior by documenting that retention policies are not retroactive, and provides CLI guidance for purging existing terminal workflows.
Changes:
- Added a warning that retention policy updates only apply to workflows that newly reach terminal states after the policy is active.
- Added Dapr CLI examples for retroactive cleanup using
dapr workflow purgeanddapr workflow list --filter-status. - Linked to the “How to: Manage workflows” doc for additional purge details.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
...ent/en/developing-applications/building-blocks/workflow/workflow-history-retention-policy.md
Show resolved
Hide resolved
...ent/en/developing-applications/building-blocks/workflow/workflow-history-retention-policy.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Signed-off-by: Josh van Leeuwen <me@joshvanl.dev>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Clarify that adding or changing a retention policy does not retroactively purge workflows already in a terminal state. Include CLI examples for retroactive cleanup using
dapr workflow purge --all-older-thananddapr workflow list --filter-statuscombined with purge.