Here’s a few thoughts…
I tend to turn off action logging for anything other than errors. But I think some people likely benefit from say checking a draft that was auto archived or trashed, to see what action was run to do that and perhaps where it was shared to as part of that process.
Other than to archive action log entries older than X, I don’t think I would ever pay much attention to this. Mainly because I set successful actions not to log.
Version histories I guess covers two areas - drafts and actions/groups.
For the former, I find the version history very useful, and honestly, because I don’t keep a lot of long term storage in Drafts, I don’t think my version history will ever be an issue. But, I wonder if an option to compress draft versions might be worth considering?
For example, prune drafts created more than 6 months ago, but rather than pruning all versions, maybe all but the oldest version on a particular date?
Another option might be to prune all drafts to only retain the last X number of versions. This could be done by date too.
For example, prune drafts not modified in the last 6 months, but rather than pruning all versions, prune them down to a maximum of X versions.
I use action versions a little, but not a great deal. But I get the feeling that an X number of versions would be a good way to trim them. Irrespective of date. I think actions are less frequently updated than a draft and the content is less likely to change significantly over a wide range of versions.
Being able to go back a version or three and back out changes or compare previous approaches has definite benefits, but I think if you want more than that, working with a full version control system might be a better fit.
Having some options to export would be useful - just in case, and just for reference rather than full restore. But I think actions could already cover that for drafts versions; not for actions/groups though or for action logs.
Functionality & Space Utilised
Given the minuscule amount of space these things take up, I wouldn’t lose any sleep over this functionality. Anything as an option would be an improvement. But, I wonder where people’s space is being used up?
I think what might be interesting is to know just how much space Drafts is “using”. It looks to me like the database, preferences, etc. is taking up a little under 50 MB for me. Is that small, medium or large for a Drafts user?
My iCloud Drive folder for Drafts on the other hand is 835 MB. I’d go out on a limb and say that’s on the large side for a Drafts user. It turns out I have ~270 MB of action backups, ~520 MB of drafts backups, and the remaining ~45MB is stuff going in out and through Drafts.
Yes, I do have both sets of backups set to retain "all’
For me, I think Drafts is using almost 0.9 GB - the majority of which is my backups. As a result, I think visibility for users on these areas and some sort of guidance as to where the space is being taken up and the options Drafts could offer to clear these down, or manage these, would be a good way of approaching this rather than just settings. Settings or inbuilt actions would be good, but combining this with some sort of basic assessment for the user would probably help the less technical Drafts users.
Hope that helps.