Related to this issue.
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
Environment: Staging (for the moment)
Hi @Vincent_Attali,
At the moment of this message, I see your schema updates (our side) dates as the following:
Do you confirm there is a lack of updates?
A refresh of your staging has been done, please confirm if it’s ok now.
Thanks a lot. Working now. We’ll see in production 
1 Like
Hi again.
Same problem now in local environment with clean and full re installation.
I’ve refreshed dev too, is it better?
I will investigate to try to find if there is a recurrent issue behing this.
Can you please confirm the schema change is uniquely about adding fields?
Thanks
Hello, i have the same problem.
We updated the schema yesterday removing a n-m relation and adding a 1-1 relation.
We have three environments, Production Staging and Development.
Production is using database_prod and Staging/Development is using database_dev.
Updates to backend are made with a GitHub action that deploy the same codebase to prod and staging environments.
Now the staging and development env are updated and we see the new fields and relations.
Production did not update.
We also tried to connect Production env to Dev database to check if there is a mismatch on database but they are identical and didn’t work.