Glad to hear that you were able to fix it with a backup. I don’t believe we had anything like this reported back in 3.5 when those changes were made, so it could be possible that it’s caused by the larger jump in version.
If it happens again, would you be able to check the system logs to see if any errors are printed? That would give us a better idea of what’s going wrong in case someone else runs into this problem