Storage limits
A hard storage limit deletes files to bring usage back under the cap, oldest first. That is by design. Read this page before enabling one.
Soft limit
Enforcement off. You get an email when usage crosses each notification threshold; nothing is deleted and nothing is blocked.
This is the right setting for most workspaces. It gives visibility without risk.
Hard limit
When total active storage exceeds the target, Rescale deletes files until usage falls below it. The oldest files go first, regardless of whose they are or which job they belong to.
Deletions are permanent: Rescale keeps no backup.
Deletion is by file age, not by size or importance. An old baseline mesh that many jobs reference is a more likely casualty than last week's large output.
The timing gaps
Two delays matter, and both can cost money:
Storage itself is tracked in real time; only the enforcement and notification passes are periodic.
If you exceed a billing tier during that hour-long window (even with a limit set inside the tier) you are billed at the higher tier for the overage.
Enforcement caps your stored volume eventually. It does not guarantee your bill stays inside a tier.
What counts toward the limit
Active storage: everything available to you on the platform. That includes files in the trash and archived files: see the file lifecycle.
Emptying the trash is what reduces the number the limit is measured against.
Setting a limit
Admins configure the target GiB, notification thresholds, and the Enforce toggle in the admin portal. See How to set storage and data transfer limits.
A hard limit is also, deliberately, the fastest way to clear a workspace's storage entirely, set the target very low and let the sweep run. How to delete all files via hard storage limit
Related
- Transfer limits — the other cap, with different behavior
- Retention policy — the separate mechanism that empties trash
- The file lifecycle — which states count
- Billing reports — how the charge is computed