Just to follow-up, nearly certain we resolved this bookmark error message issue 1.5 weeks ago with a new update. If I understood the issue correctly, there was a flaw in our database migration, which messed up an index, which meant certain operations were not possible, returning those 500 errors.
About 10 hours again we did one more update that we hope sorts out any lingering issues. 