New 6.1 annoyance - attach to existing job

System

One of my users was complaining that some of his jobs were getting trapped in our datadeploy failure task. Upon closer investigation, it turned out that the ones that were failing had an attached file with no metadata. Tagging is the first step in all of our workflows, so I was a little curious how this had happened. It turns out that he had attached the file to an existing workflow (which of course, was already past the tagging step).

Is there a way to disallow attaching a file to an existing workflow? Or to cause it to force the entire workflow back to the start task when a new file is attached?