Thanks for getting in touch. I’m really sorry you’ve run into this problem. The [ and ] characters were causing variable expressions that used output variables from steps with brackets in their names to fail without explanation. We added validation to the step names but have since realised we need to provide the ability to repair existing steps the are invalid. It’s an embarrassing oversight on our behalf.
We will be implementing a better solution to this very early in the new year, but in the meantime you can work around it a couple of ways:
Temporarily install 3.2.2 and fix your step names (removing the [ and ] characters), then upgrade to 3.2.11 (or later). This should be a safe operation, but it always makes sense to do a backup beforehand.
Update the step names in your SQL Database directly.
I know you’ve worked around this issue, and I’m sorry you encountered it in the first place. Just wanted to let you (and others) know we’ll be shipping a fix for this in 3.2.16.