I could be wrong here, but I do not believe that it's possible to retrieve anything but the latest retry of a queue item. Because of that, it should only be possible to untag the most recent exception item. I think it used to be possible, which is why there are some legacy inputs/outputs available in some actions that don't really function correctly or don't function at all. For example, when you mark an item as an exception, there is an output called 'New Item ID', but it will always output the same Item ID that the original item had, at least in newer versions of Blue Prism.
I think the basic reason for this is that items used to get unique IDs even for each retry. I cannot actually remember if that ever worked since I started using BP around v5.0.24. I probably just didn't think about it at the time.
So, I would imagine your workaround options are to either (1) edit the tags in the database if you need to handle existing items or (2) always untag items before marking them as an exception or perhaps as soon as you pick up an item that is being retried. If your goal is to lighten the database, I would consider archiving old Work Queue Items so that they're not bogging down the database, and then at the same time start ensuring that your developers use fewer tags. I'm guessing that there isn't consistency in what is tagged. The basic sort of 101 rule for tagging is that they're intended to be used for management information, and unique data shouldn't be in them.
------------------------------
Dave Morris
Cano Ai
Atlanta, GA
------------------------------
Dave Morris, 3Ci at Southern Company