ResolutionPolicy

Controls how the restore engine resolves references in a ReplaySave when the saved identifier is ambiguous — for example when a commit recorded a node by both uuid and id, but the current project has no node matching that uuid and there is exactly one node matching the id.

public enum ResolutionPolicy

Fields

Lenient 0

Accept a match by human-readable id when the uuid is not found. This is the default and handles the common case where a project was re-exported and nodes retained their id but received new uuids. An accepted fallback is recorded in Warnings with code "replay.uuid_resolved_by_id".

Strict 1

Require an exact uuid match for every commit entry. Id-only fallback is treated as a resolution failure and handed to the active RecoveryMode (skip or abort). Use this during CI or canary testing to surface uuid drift early.

Remarks

Pass your chosen policy as the resolutionPolicy argument to RestoreFromJson(string, RecoveryMode, ResolutionPolicy). The default is Lenient, which accepts id-fallback; use Strict when you want to catch uuid drift early.

Docs last synced: 2026-07-08
Screenshot viewer