Forum Discussion
Fabric keeps deleting files!!
- 1 month ago
Hi alloowishus,
Thanks for providing the additional details and for clarifying the sequence of events.
Based on your description, the workspaces were not connected to Git, and you did not perform any other workspace operations during the 3 to 4 day period. Therefore, the Git-related deletion scenarios discussed earlier do not appear to apply to this situation.
The fact that multiple workspaces were affected and that the semantic models, reports, and folders were all missing is important context. To help narrow down what may have occurred, could you provide the approximate date and time when you last confirmed that the items were present and when you first noticed that the workspaces were empty?
If available, any relevant activity or audit information from that timeframe would also be helpful. If the issue occurs again, providing the steps leading up to the behavior, along with the affected workspace and item types and approximate timestamps, would help with further investigation.
Thank you for the additional information.
A few points indicate that Git is not in play here. One of the workspaces that had been deleted was in no way linked to Git, and Git only removes items that are not found in the branch you are synchronizing with; it is impossible for it to empty a workspace that is not connected. Hence, the explanations based on branch synchronization do not apply in this situation.
The fact that in more than one newly created workspace the entire workspace, including all of its folders, is empty, and that the same thing occurs with a colleague, usually shows that the problem is due to the workspace's capacity and not to the items contained in it. The most common reason for this is that the trial capacity has expired, or that the capacity has been paused or deleted. When the capacity that supports a workspace is removed, the workspace loses its home, and its contents can therefore be deleted.
Worth checking, in order:
1. Which capacity are these workspaces on? When you check the capacity in the Workspace settings under License info, is it shown as a Trial (FT)? And in that case, is the trial currently active, and when will it expire? A trial ending is the most frequent cause of this particular symptom.
2. In the admin portal, when checking the capacity settings, it is necessary to verify that the capacity is still there, is active, and not paused; if the admin had deleted or paused it, then the workspaces associated with it will be affected.
3. The exact answer can be found in the audit log; if you filter it to show events relating to workspace and item deletions for the affected workspaces, you will see what caused it and when, either a person, a capacity change, or an automated process, and thus turn guessing into knowledge.
If it turns out to be a trial, moving these to a paid F capacity and keeping Git connected so the definitions survive will stop the bleeding. But confirm it in the audit log first.