Fix: Implement batched deletion to prevent SQL timeouts with large workflow instance datasets #7098
+269
−7
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.
Problem
Bulk deletion of 300K+ workflow instances causes SQL Server timeouts (30s default) and application crashes. The current implementation loads all instance summaries into memory and executes a single DELETE statement.
Changes
Configuration
ManagementOptions.BulkDeleteBatchSize(default: 1000) to control deletion batch sizeBatched Deletion Algorithm
WorkflowInstanceManager.BulkDeleteAsyncto process deletions in configurable batchesOffset=0(records shift up post-deletion)DeleteAsyncwith filtered ID listTesting
Configuration Example
Impact
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.
This change is