Settings

Retention

Record history and the events behind it are kept separately, so each one is its own answer. Both govern what your connected environments archive.

Record retention

How long captured record history is kept, and the point at which the archive starts making room.

Keep all history

Nothing is ever deleted. You pay for the storage it takes, or connect storage of your own.

Keep rolling history

Versions other than the latest are kept for the window you set, up to 365 days.

Maintain a maximum size

The archive is held at a size you set, dropping the oldest versions first.

Retention level, in days

How long versions other than the latest are kept. Up to 365 days.

Occupancy rate, in percent

Deletion starts only once the archive reaches this share of its allowance.

What this means

Versions other than the latest are kept for 120 days. Nothing is deleted until the archive reaches 90% of its allowance.

Event retention

How long the captured events behind those versions are kept.

Keep all events

No captured event is deleted. You pay for the storage the log takes.

Keep a rolling event log

Events are kept for the window you set, up to 365 days. There is no latest event to hold back, so the window covers every one.

Maintain a maximum size

The event log is held at a size you set, dropping the oldest events first.

What this means

The org keeps every captured event and pays for the storage it takes.

MeshERP data retention

How long MeshERP keeps the operational records that belong to your org rather than to a connected environment. The up and down proxy log is one of them.

These records are kept for 180 days.

Changing this from here is planned.