Currently, when new headers have been converted in a folder, the convert-headers task will throw an error if it's executed again, saying that new headers already exist. This workflow followed the idea that the convert-headers task would only run once (presumably for each version of the folder).
After revisiting this task and how we can use it, it would be beneficial for it to be executed by each team member on their existing 7.2 content. This would require the task to allow new headers to be present while converting old ones.
Update the task to allow for this scenario.