My Personal Environment has only been in use for approximately 6 days.I have created only one small application (BookMngmt) containing one module, one entity, and two records.
However, the database usage is currently:
In Service Center → Factory → Modules → Delete old Module versions, there are no module versions available for deletion.
Service Center reports:“130 Module versions are excluded from this list because they are used in tagged versions of applications or solutions.”
The Applications and Solutions lists mainly contain standard OutSystems system components such as LifeTime, System Components, App Feedback, etc.
Could you please investigate why a newly provisioned Personal Environment already contains approximately 2.6 GB of System Data, and perform the necessary cleanup/unblock?
Please also confirm whether the retained tagged system versions are responsible for the excessive System Data usage.
What you’re seeing is a known situation with some Personal Environments: a very small amount of your own work, but a very large amount of System Data due to:
Since you’ve only used the environment for ~6 days and have a single small app, the numbers you report (≈2.6 GB System Data, 130 excluded module versions) almost certainly come from those tagged system module versions, not from your BookMngmt app.
Personal Environments have a fixed 2 GB DB limit. System Data includes:
When OutSystems upgrades or maintains Personal Environments, it can leave multiple module versions for core apps tagged in LifeTime/solutions. These versions:
So yes: the retained tagged system module versions are very likely responsible for most of your 2.6 GB System Data.
You already checked:
Those excluded versions:
Forge tools like DB Cleaner / DB Cleaner on Steroids / OneClickCleanup can help remove your own old module versions and deleted entities, but they cannot safely remove those tagged system versions in a cloud Personal Environment. Even if they show up, deleting them would risk breaking the environment.
For Personal Environments that:
the recommended action is:
Open a Support Case with OutSystems. Support can: Unblock the environment Run internal cleanup routines on system data Remove or compress old tagged system versions that you cannot touch yourself Validate that nothing critical is removed Manage the database space of your personal environment [[After updating to Version 11.7.3 (Build 5968), Database Usage of Systems Data is 100%<>https://www.outsystems.com/tk/redirect?g=1cce0408-ea1a-4fac-9ed2-fb216a25aec9]]
Open a Support Case with OutSystems. Support can:
In fact, the documentation for Personal Environments explicitly states:
If the personal environment becomes unavailable or usage reaches 100%, it will be necessary to open a Support Case with OutSystems to unblock the environment and suggest specific cleanup actions. Manage the database space of your personal environment
In your Support Case, I suggest you include (you already have most of this):
This is precisely the kind of case where OutSystems Support needs to act; you’ve already done the right checks on your side.
There’s not much you can do about the system modules themselves, but you can:
But for the current situation, the system data is clearly the main problem, and only Support can address it in a Personal Environment.
Direct answer to your two final points:
“Could you please investigate why a newly provisioned Personal Environment already contains ~2.6 GB of System Data, and perform the necessary cleanup/unblock?” Investigation and cleanup/unblock must be performed by OutSystems Support, not via Service Studio/Service Center alone. Please open a Support Case and include the details you shared.
“Please also confirm whether the retained tagged system versions are responsible for the excessive System Data usage.” Based on the numbers and the “130 module versions excluded due to tagged applications/solutions” message, yes, those retained tagged system module versions are almost certainly responsible for most of the excessive System Data usage.
Since you have already attempted the built-in Service Center cleanup tool and found no versions available to delete due to system locks, you must escalate this:
@hoang thanh thanh : It is highly unlikely that a Personal Environment would fill up this much unless there have been a large number of publishes, or the module itself is quite large.
Please go to Service Center -> Your Module -> Version and check how many versions you have published so far.
Then, go to Service Center -> Export -> Save As -> Save As and save the OML file to your local machine. Check the size of the OML.
As a rough estimate, you can multiply the size of the module by the number of publishes to get an idea of how much space the module versions could be consuming in System Data.
For example, if your module is 3 MB and you have published it 100 times, that alone could account for roughly 300 MBof storage.
You can also remove any unused dependencies, which may help reduce the module size.
Regarding deleting old module versions, Service Center does not provide an option to manually delete versions that are less than one week old. You can consider using DBCleaner to clean up old module versions and other unnecessary data.