Feature(s) impacted
I lost my entire layout configuration that I had spent literally hours configuring.
Observed behavior
I don’t see my tables anymore. Worst, it looks like I need to reconfigure E.V.E.R.Y.T.H.I.N.G 
Expected behavior
I just want my layout not to disappear of all a sudden without me even clicking on “Edit layout”.
Failure Logs
I can’t see any errors in the logs as far as I can tell.
Context
- Project name: Fairmint Series
- Team name: Fairmint
- Environment name: Dev_database and Production
- Database type: Postgresql
- Recent changes made on your end if any:
We simply rotated our database credentials (user name and password).
I updated the .env file of the agent to reflect the new credentials.
At first, it seemed to be working (the data was showing and I was having no errors in the logs), but then we realized that there was no more any “related data”, which is super annoying because this is how most of the navigation is done. So we tried to understand what could be happening, we never edited the layout. We mostly tried to:
(a) stop / start the server => nothing changed
(b) copied the .forestadmin-schema.json from a previous working version => nothing changed
(c) push a few changes (4 if I recall correctly) that were done in Dev_database but hadn’t been deployed to Production
If I remember well, it is at this moment that, when we reloaded the forest admin, we saw that all our layout was gone. At first, we just it was probably an issue with the .forestadmin-schema.json so we tried to run the agent locally, to rebuild a .forestadmin-schema.json from scratch and then copy it to our Dev_database and Production environment… but it didn’t work.
Then, I clicked on Edit layout and saw with horror that all the tables were actually hidden, all the organization that I had made was reset and all the configuration on each table was also reset… A vision of horror that made me stop everything and come ask for help here.
If you could restore my layout, you will save me literally hours and hours of work 
Also, I suppose this is related: we really need to have the “Related data” navigation back, I don’t understand how we lost it in the first place.
Finally, I must say that It is not normal that updating the credentials somehow led to wiping out hours of work.
And, if you are self-hosting your agent:
- Agent technology: nodejs
- Agent (forest package) name & version (from your .lock file): 1.64.5 (I updated it, thinking it might be the issue… but no). Before that, I think it was 1.50 but I am not 100% certain.
Please help
Hello @thibauldf
It seems you have pushed a forest schema without any collection on your Production environment on Tue Jul 15 2025 03:49:38 GMT+0200 (Central European Summer Time), I can communicate you the ip address that pushed the change if you want (it seems to be the same as the previous pushes). Which removed all layout customization on your project.
The faulty schema is still present on your Production environment.
This could happen when synchronising a database with no tables.
As you do not have the required plan, there are no backups of your layout, sadly I am not able to restore it to its previous state.
Pushing back your old schema by resetting correctly the database variable in your environment file will restore your collections, actions and any changes you made through the code of your agent. But it will not restore the UI modifications you made on forest.
Nicolas
Thank you for the answer but it is really hard to swallow because I certainly did not WILLINGLY push a forest schema without any collection to Production. As a matter of fact, I still have a tab opened on “what was there before” I pushed:
As you can see, I have my full layout with configuration and all. At the top it says “4 changes” pending. That’s what I pushed to production, as you can see on the screenshot, I did not push a “forest schema without any collection”. What more likely happened is that there was a bug in your app that wiped out my layout when I pushed!
Now, that being said, how can I recover my layout? I am the kind of guy who makes a copy of everything. I always make sure to backup my .forestadmin-schema.json before updating anything:
But I can only backup what can be backed up! If now you’re telling me that my layout cannot be recovered because I couldn’t back it up and you did not back it up, it’s 100% unacceptable. You should put in red in your pricing page: “Beware, we may have bugs that will wipe out your data without any ability to recover it”. I can understand that you have a plan that doesn’t offer version control to customers… but it doesn’t mean that internally you should not do it, exactly for cases like this one! Losing data is never acceptable.
Given what you’re saying, the only hope I have now is that I have a slightly outdated layout running on my local agent. Is there a way to at the very least recover that layout? It’s still a pain, but it would be sooooo much better than restarting everything from scratch!
Happy to move to DM or hop on a zoom, whatever works best to get this solved.
Let me know
cc @arnaud
Can I please have an answer @nbouliol @arnaud ?
All my team is blocked because of this, it is a red alert here 
If you can solve our issue, I’ll happily upgrade to whatever plan works (note that I am already a paid customer!).
As I said in my previous message, I can hop on a call, DM, telegram, zoom… you name it but I need to get this resolved asap.
Can I please have some news guys?
I am so desperate that I am even willing to spend the time reconfiguring everything instead of trying to recover the layout I had (note that I would still love to recover the layout that I have running on my local agent if it’s possible, just let me know how)… but I cannot do it until I am 100% certain that I won’t lose my work again!
What is the proper way to backup one’s configuration? Clearly, saving the .forestadmin-schema.json isn’t enough it seems. What else should I do to be 100% certain I won’t lose my data?
Hi @ThibaudF,
I’m truly sorry to hear about this and I understand your frustration. As @Nbouliol explained, it won’t be possible to retrieve your previous configuration because you were on a Team plan, which does not include this option.
However, I do have some good news for you. I have activated this option that will allow you to restore a previous layout starting from today, in case of any further issues. That’s unfortunately the best we can do right now.
We can discuss this further if you want, here is my calendar:
https://calendar.app.google/1SnMVR5PDVu1caSw7
1 Like
Thank you @lionel.bouzonville ! It reassures me a lot to know that, moving forward, we have a safety net regarding our config data. Honestly, if I were you, I would just enable that for every single customer (even in the background, without telling them or giving them any new feature). The ability to recover from data loss that occurred from bugs in the app should not be a pricing option.
I’ll rush to finish reconfiguring 80% of our workspace today and I booked a meeting for tomorrow.
Thanks!
2 Likes
