Botpress 12.2.0 not saving any changes

Upgraded to 12.2.0 to fix some timeout issue, but now Im unable to save any changes to botpress.
At first I had errors with HITL, ended up adding the column manually because the migration didnt seem to work.
Then I had errors with analytics, that was trying to insert two rows with the same keys. I disabled the module to make the error go away.
Now, I’m unable to save. No errors are showing up. In my log I can see ::

Nov 05 10:37:45 dev-botpress-1 bp[29138]: 10:37:45.979  2019-11-05T15:37:45.979Z bp:api:request /api/v1/bots/pierrepaul2/flow/main.flow.json { method: 'POST', ip: 'xxxxxxxxxxx', originalUrl: '/api/v1/bots/pierrepaul2/flow/main.flow.json' }
Nov 05 10:37:45 dev-botpress-1 bp[29138]: 10:37:45.981  2019-11-05T15:37:45.981Z bp:audit:collab:success /api/v1/bots/pierrepaul2/flow/main.flow.json { method: 'POST', email: 'xxxxxxxxxxxxx', operation: 'write', resource: 'bot.flows', userRole: 'superAdmin', ip: 'xxxxxxxx' }
Nov 05 10:37:45 dev-botpress-1 bp[29138]: 10:37:45.983  2019-11-05T15:37:45.983Z bp:api:request /api/v1/bots/pierrepaul2/content/elements { method: 'POST', ip: 'xxxxxxxxxx', originalUrl: '/api/v1/bots/pierrepaul2/content/elements' }
Nov 05 10:37:45 dev-botpress-1 bp[29138]: 10:37:45.985  2019-11-05T15:37:45.985Z bp:audit:collab:success /api/v1/bots/pierrepaul2/content/elements { method: 'POST', email: 'xxxxxxxxxxx', operation: 'read', resource: 'bot.content', userRole: 'superAdmin', ip: 'xxxxxxxxxxxxx' }

You can check a demo of the issue : https://youtu.be/hejlxdcVl9E
Any tips on how I could debug this issue?

So, testing locally with sqlite worked just fine.
Decided to give it a go and created an empty postgresql database and it worked perfectly.
Im guessing the upgrade path was not perfect.

I lost my workspace_users and my conversations, but I can live with that.
If someone at Botpress wants a copy of the DB (before and after), let me know.
Both databases don’t have any confidential information for now.

Hey @PierrePaul ! That’s kind of important, what was your previous version ? Did you upgrade from 12.1.6 ?

No, we were at 12.0.1 I think, or maybe even 12.0.0.

Thanks for reporting this, I’ll do some tests on my side and make sure migrations don’t break.

Can you send us your DB before/after? We’ll try to replicate the issue
(I believe you have my email)