Hi @Lewenhaupt, rebuilding the entire module from scratch must have been tedious. I'm sorry your team had to go through that. I have not been able to find other reports of this issue and I'm unable to reproduce it. If you share the JSON with us, we could take a closer look.
Did we try using previous versions of the module through history or release versions? Knowing what type of migration was done to the module would also give us more context to try and recreate this bug.
​
We are doing our best to get back to all of our users as fast as possible given the increase in volume of questions on the forum.
Thank you for your patience and understanding! 
PS: You could join Office Hours to get live help on Tuesdays and Thursdays at 11am-12pm PST.