# Test environnement schema don't update **URL:** \ **Category:** Help me!\ **Created:** [July 23, 2020, 8:10am UTC](https://community.forestadmin.com/t/test-environnement-schema-dont-update/714 "2020-07-23T08:10:50Z")\ **Posts on this page:** 19\ **Page:** 1
**Author:** ![Bruno\_Maurice](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/bruno_maurice/32/573_2.png) [@Bruno\_Maurice](https://community.forestadmin.com/u/Bruno_Maurice)\ **Post date:** [July 23, 2020, 8:10am UTC](https://community.forestadmin.com/t/test-environnement-schema-dont-update/714/1 "2020-07-23T08:10:50Z")
## Expected behavior I expect my environnement to follow the model structure build on the .forestadmin-schema file. ## Actual behavior The test environnement never update ## Context We use the express forest-express-sequelize version “6.1.4”. Our file .forestadmin-schema is correctly build since our local environnement apply new change. I did verification on the docker build that the forestadmin-schema is like expected. We have only this issue with our test environnement. The preprod environnement have all update apply (the build is actually the same). Project : Askeet ---
**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:** [July 23, 2020, 8:39am UTC](https://community.forestadmin.com/t/test-environnement-schema-dont-update/714/2 "2020-07-23T08:39:43Z")
Hi @Bruno_Maurice 👋 welcome to our community. The `.forestadmin-schema` file is normally built only on a `dev` or `development` `NODE_ENV` on server start. You should normally commit this file with your code base. Have you got any error logs ? ---
**Author:** ![Bruno\_Maurice](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/bruno_maurice/32/573_2.png) [@Bruno\_Maurice](https://community.forestadmin.com/u/Bruno_Maurice)\ **Post date:** [July 23, 2020, 8:41am UTC](https://community.forestadmin.com/t/test-environnement-schema-dont-update/714/3 "2020-07-23T08:41:56Z")
Hi @Arnaud_Moncel thanks for your quick answer. The file is commit and present with all change on the running instance. Unfortunately I have not error log :s Something realy strange is that some change apply on test have been deploy with the rest of the application on preprod and the schema have been update on preprod environnement but not in test environnement where the code was originaly present. Its realy the test environnement who bug. ---
**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:** [July 23, 2020, 9:44am UTC](https://community.forestadmin.com/t/test-environnement-schema-dont-update/714/4 "2020-07-23T09:44:50Z")
It seem to have a desynchronization of your `test env` schema on our side. Can you confirm me that your last deployment dated from 20/07 ? These three schema must be identical? ---
**Author:** ![Bruno\_Maurice](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/bruno_maurice/32/573_2.png) [@Bruno\_Maurice](https://community.forestadmin.com/u/Bruno_Maurice)\ **Post date:** [July 23, 2020, 9:58am UTC](https://community.forestadmin.com/t/test-environnement-schema-dont-update/714/5 "2020-07-23T09:58:15Z")
We have deploy more change yesterday 22/07. We deploy new change yesterday that did not apply ether so no it should be a slightly different of the preprod env ---
**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:** [July 23, 2020, 10:15am UTC](https://community.forestadmin.com/t/test-environnement-schema-dont-update/714/6 "2020-07-23T10:15:12Z")
To be sure I understand you tried to deploy on your `pre-prod` env from your `test` env and the change not be applied, right ? ---
**Author:** ![Bruno\_Maurice](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/bruno_maurice/32/573_2.png) [@Bruno\_Maurice](https://community.forestadmin.com/u/Bruno_Maurice)\ **Post date:** [July 23, 2020, 10:30am UTC](https://community.forestadmin.com/t/test-environnement-schema-dont-update/714/7 "2020-07-23T10:30:12Z")
A no. We did some dev last week on branch develop that have been deploy on test env. This dev should updated some field and relation and custom field of our FA schema (it did localy). But the schema never update on FA test env. We merge develop into our master that have been deploy on preprod since we had feature to release more importante that juste the FA schema change. We notice that the FA env preprod got all schema update that wasn’t apply on FA test env. Yesterday we did some other change locally that have been deploy on test but the FA test continue to don’t synchronise the change we did. It’s like test env don’t care that the `forestadmin-schema` have some change. ---
**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:** [July 23, 2020, 12:51pm UTC](https://community.forestadmin.com/t/test-environnement-schema-dont-update/714/8 "2020-07-23T12:51:22Z")
Do you have this kind of env var `FOREST_DISABLE_AUTO_SCHEMA_APPLY` set in your `.env` file on your test environment ? ---
**Author:** ![Bruno\_Maurice](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/bruno_maurice/32/573_2.png) [@Bruno\_Maurice](https://community.forestadmin.com/u/Bruno_Maurice)\ **Post date:** [July 23, 2020, 12:52pm UTC](https://community.forestadmin.com/t/test-environnement-schema-dont-update/714/9 "2020-07-23T12:52:58Z")
No never see this env variable ---
**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:** [July 23, 2020, 1:48pm UTC](https://community.forestadmin.com/t/test-environnement-schema-dont-update/714/10 "2020-07-23T13:48:36Z")
I’m trying to figure out what’s going on. You say you have the correct `.schema` on `test` sever right ? Have you restart your `test` server ? Your `test` server can access `https://api.forestadmin.com/` (with curl command for exemple) ? ---
**Author:** ![Bruno\_Maurice](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/bruno_maurice/32/573_2.png) [@Bruno\_Maurice](https://community.forestadmin.com/u/Bruno_Maurice)\ **Post date:** [July 23, 2020, 1:56pm UTC](https://community.forestadmin.com/t/test-environnement-schema-dont-update/714/11 "2020-07-23T13:56:58Z")
Yes the .schema is the same as on local where the configuration work. The instance restart each time we deploy new docker version of our application. I don’t have curl on my docker but with wget I got : > /app # wget [https://api.forestadmin.com/](https://api.forestadmin.com/) > Connecting to [api.forestadmin.com](http://api.forestadmin.com) (34.241.101.223:443) > wget: server returned error: HTTP/1.1 404 Not Found I have the same result on preprod when I do a wget, so very not sure its the main issue. ---
**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:** [July 24, 2020, 7:18am UTC](https://community.forestadmin.com/t/test-environnement-schema-dont-update/714/12 "2020-07-24T07:18:31Z")
We’ve made some manipulations on our side. Let me know if your `test` environment is well synchronized now. ---
**Author:** ![Bruno\_Maurice](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/bruno_maurice/32/573_2.png) [@Bruno\_Maurice](https://community.forestadmin.com/u/Bruno_Maurice)\ **Post date:** [July 24, 2020, 7:20am UTC](https://community.forestadmin.com/t/test-environnement-schema-dont-update/714/13 "2020-07-24T07:20:50Z")
It seem to have fixe the issue. Great. Thanks for your help, really appreciate. ---
**Author:** ![Bruno\_Maurice](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/bruno_maurice/32/573_2.png) [@Bruno\_Maurice](https://community.forestadmin.com/u/Bruno_Maurice)\ **Post date:** [August 11, 2020, 2:58pm UTC](https://community.forestadmin.com/t/test-environnement-schema-dont-update/714/14 "2020-08-11T14:58:26Z")
Hi @Arnaud_Moncel I start to have the same issue now with the production env. We deploy some chance yesterday that is not accessible. I did all verification (log at start of docker, presence of the change on fa preprod env, presence of table and element on db for the prod env…) without any found. I think there is a new unsync like last time. Is it possible to have a lot at it ? It could be great to have a tool to force a sync in case of situation like that. Thanks ---
**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:** [August 12, 2020, 8:34am UTC](https://community.forestadmin.com/t/test-environnement-schema-dont-update/714/15 "2020-08-12T08:34:51Z")
Hi 👋 @Bruno_Maurice, can you enter in the edit mode and try to see if your collection is present and set to hidden like this ![image](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/1X/6e647215c080800c523320ee643af6149c0d5003.png) ? ---
**Author:** ![Vincent\_Attali](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/vincent_attali/32/654_2.png) [@Vincent\_Attali](https://community.forestadmin.com/u/Vincent_Attali)\ **Post date:** [August 12, 2020, 8:47am UTC](https://community.forestadmin.com/t/test-environnement-schema-dont-update/714/16 "2020-08-12T08:47:31Z")
Hello, We have the same problem here. We developed new features yesterday including 3 new fields (two in one table, another in a second one). All is fine in local environment with schema update, database with new fields, Forest with new fields. In our staging one, the database was also updated with our new fields but no change in Forest. The fields are not hidden, there are literally not here. I think we have the same synchronization problem as discussed here. Any idea? Have a good day, Project: Homeloop - Staging environment ---
**Author:** ![Bruno\_Maurice](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/bruno_maurice/32/573_2.png) [@Bruno\_Maurice](https://community.forestadmin.com/u/Bruno_Maurice)\ **Post date:** [August 12, 2020, 9:21am UTC](https://community.forestadmin.com/t/test-environnement-schema-dont-update/714/17 "2020-08-12T09:21:23Z")
Unfortunately the collection is not in the hidden place. (I did the same feedback at first to my client ^^’) ---
**Author:** ![arnaud](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/arnaud/32/32_2.png) [@arnaud](https://community.forestadmin.com/u/arnaud)\ **Post date:** [August 12, 2020, 4:25pm UTC](https://community.forestadmin.com/t/test-environnement-schema-dont-update/714/18 "2020-08-12T16:25:44Z")
Hi @Bruno_Maurice, We had a second issue about your production environment. It is fixed, you should now be able to access the new collections/fields you recently deployed in production. Thanks for your patience. ---
**Author:** ![Bruno\_Maurice](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/bruno_maurice/32/573_2.png) [@Bruno\_Maurice](https://community.forestadmin.com/u/Bruno_Maurice)\ **Post date:** [August 13, 2020, 6:43am UTC](https://community.forestadmin.com/t/test-environnement-schema-dont-update/714/19 "2020-08-13T06:43:08Z")
Great thanks @arnaud for you intervention everything seem good.