Lost values / Inactive Fields
When a config change removes a field (you delete it from a section type, or you change its handle), the values editors already saved for it don’t just vanish. SEK keeps them. A saved value whose field no longer exists in the current config becomes a lost value, and the editor surfaces lost values in the Inactive Fields panel so nothing is silently thrown away.
Why values get lost
Section titled “Why values get lost”A value is “lost” whenever reconciliation finds saved data with no matching field in the current config. The common causes:
- A field was removed from the section type’s
fields:list. - A field’s handle changed. Matching is by handle, so a renamed handle looks like the old field disappearing and a new, empty field appearing.
- A field moved in a way that changes its addressed path.
In every case the value has nowhere to attach under the current config, but
discarding it would make config edits dangerous. Instead the value moves to a
lostValues store on that section instance.
The Inactive Fields panel
Section titled “The Inactive Fields panel”The editor collects a section’s lost values into an Inactive Fields panel on that section. It shows what was saved under the now-inactive handle, so an editor or developer can see exactly what content is being held in reserve rather than guessing what a config change stranded. Nothing in the panel renders on the front end: these values are inactive precisely because no current field claims them.

Recovery is automatic
Section titled “Recovery is automatic”Lost values are held, not frozen. If the field comes back (you re-add the handle
to the config, or rename it back), reconciliation restores the value from
lostValues to the live field automatically on the next mount. Removing and
re-adding a field is non-destructive, and so is fixing a handle you renamed by
mistake: put the original handle back and the stranded content reattaches.
This is the practical payoff of config as the source of truth: because SEK knows precisely which saved values the current config accounts for, it can hold the rest safely instead of deleting them. A config change is recoverable, not a one-way door.