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

Ability to automatically or en mass trim old Workflows #16447

Closed
Piedone opened this issue Jul 16, 2024 · 3 comments
Closed

Ability to automatically or en mass trim old Workflows #16447

Piedone opened this issue Jul 16, 2024 · 3 comments

Comments

@Piedone
Copy link
Member

Piedone commented Jul 16, 2024

Is your feature request related to a problem? Please describe.

Executing a Workflow Type creates a Workflow document, and a corresponding WorkflowIndex. Unless you delete Workflows manually (either one by one, or in bulk page by page), this causes both the Document and the WorkflowIndex table to grow indefinitely.

This becomes a real issue if workflows are executed frequently. E.g., the site of one of our client uses Workflows to handle form submissions, which forms are submitted by thousands of people every workday. The result is that the Document table is now 12 GB with 860k rows, and the SQL query behind /Admin/Workflows/Types (SELECT DISTINCT [WorkflowIndex].[WorkflowTypeId] FROM [WorkflowIndex]) times out, resulting in an error page.

Related to #6056.

Describe the solution you'd like

A feature that would periodically delete Workflows older than a given threshold, much like Audit Trail trimming works, would be ideal.

This needs special care and batching, since there can be a huge number of Workflows (860k for us), especially the first time it runs.

Describe alternatives you've considered

The ability to delete Workflows en mass mass, more than just 10 items on a page.

Copy link
Contributor

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.

@deanmarcussen
Copy link
Member

possibly duplicate of #11609

We actually wrote this internally (pruning/trimming), and have been wanting to pr it back.

With any luck that might actually happen soon

@Piedone Piedone closed this as not planned Won't fix, can't repro, duplicate, stale Jul 18, 2024
@Piedone
Copy link
Member Author

Piedone commented Jul 18, 2024

That would be awesome!

@MikeAlhayek MikeAlhayek modified the milestones: 2.x, 2.0 Sep 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants