For anyone else that comes across this a few other users were able to fix the error by optimizing their database.
We’re still trying to get more information for the developers, but if it is a database issue the best thing would be a copy of the database before the fix occurred.
