The server keeps several recent saved versions of each project. The count depends on the order status — the further the project has moved toward production, the fewer "intermediate" versions are needed, and the older ones are automatically removed.
Limit by status
| Project status | Versions kept |
|---|---|
| Draft / not placed | up to 7 most recent |
| Confirmed by the factory | up to 5 most recent |
| In production | up to 3 most recent |
| Ready to ship or shipped | 1 (the most recent) |
The limit applies during automatic cleanup. If you already have 7 draft versions and you make an 8th save — the oldest draft version makes room for the new one. This happens "silently", without any confirmation.
30-day protection
Versions younger than 30 days are not removed automatically even when the limit is exceeded. That is, in the first 30 days after saving, no one touches your version — even if you've made another 20 edits on top.
After production confirmation
When the factory confirms the order for production, the project's status changes — the storage limit goes down. Some historical versions will gradually be removed. This is intentional: after production starts, what matters is the last agreed revision, and older intermediate variants are no longer needed.
If you need to keep a specific old version "forever" — discuss this with the factory (for example, exporting to a file, a fixed archive order).
If the version you need isn't in the list
- It may have been removed by the limit — check neighboring dates; a version close in content may be there.
- Contact your manager at the factory — the factory may have backup copies of orders.
- For the future: before major edits, click "Save" — this creates a new version in history, and if needed it's easy to return to that point.
Related topics
- Switching between saved versions — how to open an older revision.
- Saving the project to the server — how a new version is created.
- Version mismatch: memory and disk — if the local draft doesn't match the server copy.