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

Clear execution history of a flow #4697

Open
hiagodotme opened this issue May 15, 2024 · 0 comments
Open

Clear execution history of a flow #4697

hiagodotme opened this issue May 15, 2024 · 0 comments
Labels
🧹 clean up Things are no longer needed ⭐ enhancement New feature or request

Comments

@hiagodotme
Copy link

Is your feature request related to a problem? Please describe.
Yes and no, I have a flow that runs every two minutes.

The output of this execution is only used for validation and detection of possible problems in the flow. I use SQLite, I preferred not to install Postgres. My problem is that the file is getting big and I would like to be able to remove these histories.

Describe the solution you'd like
I have several ideas for this. The first one is a simple UI where I enter the time interval and click a button to clear it.

This interface could be on the screen that shows the runs, a filter could be used to exclude them precisely. The filter could contain the information below:

Flows:
- All
- Flow A...
- Flow B...
- Flow C...

Delete everything before: a date field, which when filled in, the person could choose from when they want to keep it.

Result:
- All
- Success
- Failure

When filling in the filter data, a confirmation interface is displayed stating: You will delete 31,560 execution histories.

Upon confirmation, a hard delete on the database is performed.

Describe alternatives you've considered
In contact with the Discord people, the suggestion was given to me to "duplicate the flow" and delete the old one.

Perform a DELETE directly on the database for the flow_run table.

In my case, the first option will help, because I don't use webhook in these flows and I also couldn't access the SQLite database (it's encrypted).

But if I used the webhook, I would have problems. Because you would have to reconfigure the locations that trigger the webhooks.

Additional context
I believe that in the flow itself, we could set a retention time. And what we wanted to keep for how long, example:

Successful executions remain recorded for 15 days.

Failed executions last for 2 months.

@abuaboud abuaboud added ⭐ enhancement New feature or request 🧹 clean up Things are no longer needed labels May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🧹 clean up Things are no longer needed ⭐ enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants