Per workflow prunning of execution data?

The idea is:

Enable workflow setting for execution data prune

My use case:

I have a workflow that listen to my mail inbox every minute to detect and triage automation workflows. this generates a lot of exectuion and I want to prune them based on timeout.

My challange is that

  • I’m not the only one using this self-hosted n8n, and this is not the only workflow, so I can’t simply update the environment variable to change the global prunning setting ( as suggested here : Execution data | n8n Docs)
  • I can not simply rely on success or failure of the workflow, since even the success flow may contain troubleshooting data when my workflow is not working as I expected.

I think it would be beneficial to add this because:

If we can enable something in the workflow settings that can work similarly with the EXECUTIONS_DATA_MAX_AGE and EXECUTIONS_DATA_PRUNE_MAX_COUNT similar to server setup, that allow workflow to override the server settings if it’s set to more strict ( e.g. global level 180 day, workflow level 3 day, then 3 day is in effect, if global is 180 day, and workflow level 360 day, then 180 day is in effect, similarly for max count)

Any resources to support this?

Are you willing to work on this?