# \`This schema does not exists\` when running \` forest schema:update\`

**URL:** <https://community.forestadmin.com/t/this-schema-does-not-exists-when-running-forest-schema-update/5796>\
**Category:** Help me!\
**Created:** [January 5, 2023, 9:48pm UTC](https://community.forestadmin.com/t/this-schema-does-not-exists-when-running-forest-schema-update/5796 "2023-01-05T21:48:52Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Arnaud\_Moncel](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/arnaud_moncel/32/24_2.png) [@Arnaud\_Moncel](https://community.forestadmin.com/u/Arnaud_Moncel)\
**Post date:** [January 11, 2023, 8:20am UTC](https://community.forestadmin.com/t/this-schema-does-not-exists-when-running-forest-schema-update/5796/8 "2023-01-11T08:20:16Z")

</div>

> [@Brett\_Belka](#):
>
> However, it didn’t update the existing models files. Rather, it produced duplicates. Of everything.

Do you run the update command with some options ?  
This command should only create missing models, route and forest files. To really update models after a column addition in the database or something like that you should remove impacted models and re-run the command.

---

_[View the full topic](https://community.forestadmin.com/t/this-schema-does-not-exists-when-running-forest-schema-update/5796)._