Hi @SVB,
We’re still discussing this internally. Rolling back to a previous database version until this issue is resolved is definitely an option, but would also mean that certain mp-ids would go temporarily “missing”, which is problematic for other reasons. This might however be the best option for the time being.
Beyond this specific issue, we’re also discussing ways to better share historical versions of the database, and to allow users to opt-in to preview new versions of the database, so that we can better handle this in future if any similar issues occur.
Resolving this is absolutely a priority for us. Thanks for your patience while we get it fixed.
Matt