@user19 I encountered this exact same issue when upgrading from Strapi version 4.2.3 to 4.3.8. The problem seems to occur consistently for any deployment when new schemas are added, causing a duplicated key error that prevents the server from starting properly. This issue appears to be related to how Strapi handles database migrations. Aside from the SQL script workaround mentioned in the thread, have you found a more effective and proper solution for resolving this issue? Thank you.
The following is my system information:
- Strapi Version: v4.3.8
- Operating System: linux, macOS
- Database: MySQL
- Node Version: v16.15.1
- NPM Version: .v8.11.0