If anyone else is having this issue these instructions can solve it in most situations.
The issue should be temporary due to a known bug in a earlier version of our software and it should not happen going forward.
We will try to recreate this to see if there is a way the bug continued on somehow.