# Errors after running schema:update - foreign key constraint

**URL:** <https://forum.mautic.org/t/errors-after-running-schema-update-foreign-key-constraint/25286>\
**Category:** Product Support\
**Created:** [September 3, 2022, 2:36pm UTC](https://forum.mautic.org/t/errors-after-running-schema-update-foreign-key-constraint/25286 "2022-09-03T14:36:27Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mzagmajster](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/mzagmajster/32/687_2.png) [@mzagmajster](https://forum.mautic.org/u/mzagmajster)\
**Post date:** [September 5, 2022, 4:01pm UTC](https://forum.mautic.org/t/errors-after-running-schema-update-foreign-key-constraint/25286/2 "2022-09-05T16:01:23Z")

</div>

Why do you use schema update force command in prod. env.? Please use bin/console doctrine:migrations:migrate.

Also since it seems like a problem related to incomplete migrations from the past, you might benefit from reading this: [MySQL error upgrading to 4.2 - #9 by cwmarketing](https://forum.mautic.org/t/mysql-error-upgrading-to-4-2/22867/9)

I would avoid any upgrades until you resolve the issues with migration.

---

_[View the full topic](https://forum.mautic.org/t/errors-after-running-schema-update-foreign-key-constraint/25286)._