MCS MeshERP
Configuration

Retention

How long captured record history is kept, how long the events behind it are kept, and why they are two separate answers.

Record history and the events behind it are kept separately, so each one is its own answer. They are configured on the same page but they do not have to agree with each other.

Retention. Record retention above, event retention below, each saved independently.

Record retention

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

OptionWhat it does
Keep all historyNothing is ever deleted. You pay for the storage it takes, or connect storage of your own.
Keep rolling historyVersions other than the latest are kept for the window you set, up to 365 days.
Maintain a maximum sizeThe archive is held at a size you set, dropping the oldest versions first.

Choosing Keep rolling history exposes two numbers:

  • Retention level, in days is how long versions other than the latest are kept, up to 365
  • Occupancy rate, in percent is the share of your allowance the archive must reach before any deletion starts
The latest version is never the one dropped

Rolling retention applies to versions other than the latest. Ageing out history does not age out the record itself.

The What this means box under the controls restates your two numbers as one sentence, for example: versions other than the latest are kept for 120 days, and nothing is deleted until the archive reaches 90% of its allowance.

Event retention

How long the captured events behind those versions are kept.

OptionWhat it does
Keep all eventsNo captured event is deleted. You pay for the storage the log takes.
Keep a rolling event logEvents are kept for the window you set, up to 365 days.
Maintain a maximum sizeThe event log is held at a size you set, dropping the oldest events first.
A rolling event window has no floor

Record retention always holds the latest version back. An event log has no latest event to hold back, so the window covers every one of them. Set it shorter than you think and you will lose events that the version history still refers to.

Saving

Each block saves on its own, with its own Save changes and Undo. Changing record retention does not touch event retention, and the reverse is also true.

Where retention is first set

Retention is step 4 of onboarding. This page is where it is changed afterwards.