Can also confirm this issue since 1.1 I also have a few customers with the same issue. Tested on multiple nodes to ensure it was just an issue with one, tested by creating a new scenario on GM, then saving it and attempting to load it.