After investigations, we detected a critical (and very recent) regression with the “sync database” due to the introduction of the new multi-datasource support feature.
We are actively working on a patch to prevent this in the future.
In order to restore your collections, you will have to, in your environment settings:
do an “update credentials” and put your database credentials again
click on the datasource and then “update credentials” button.
Your previous layout configuration will be unfortunately lost.
Sorry that it was not clear in our initial response (edited since), but this issue is really recent (introduced a few days ago) and limited to specific projects that did not “sync database” since the beginning of July.
As it is not a generic issue, we did not write automatic tests on this specific case, and we thus released this critical regression.
As we are finalizing the patch, we will obviously make sure to cover this case with automated tests (as specified in our internal processes for such scenario).
About the layout, we actually do have an automated layout backup system, but it is an Enterprise level feature that has not been activated on your project that is still in trial.
Such feature is here to help customers to recover their own unexpected layout manipulation in the recent past.
In your case, the layout is lost due to a Forest Admin bug. In such circumstances, we understand that we should do our best to help you restore your layout. And we can actually restore this layout, via a manual and more time consuming process for our team.
As you define your project as a POC, do you want us to spend the time to attempt this layout recovery?
Do you think it is worth the effort, according to your previous layout configuration complexity?
Thank you for your response, and sorry again for the scare…
Did you manage to recover access to your database already by updating the credentials ? I need to know before starting to perform the restore, otherwise it might be lost again.
Please note that any web hooks and code customizations that you have added to your cloud agent should be restored automatically along the database connection. You may have to check again that they are allowed by your role.
