Lifecycle Troubleshooting

What this helps you do

Work through common lifecycle setup, matching, dry-run, enforcement, scheduler, and permission issues.

If a policy is not applying, confirm the policy exists, is not deleted, has one active/current version, and has an active assignment within its effective dates. Then recalculate the document lifecycle state or run shadow backfill depending on the scope.

If a document did not match a rule, check assignment target, precedence, document folder/category/doc type, workflow template instance when using workflow scope, and whether the resolver trace selected a different assignment.

If the wrong version is active, open Versions and confirm the intended version is Active. Only one version can be active per policy; activating a new version supersedes the old one.

If the date source is missing, check the selected system field, document metadata key, or workflow metadata field. For workflow metadata, the document needs a matching workflow instance and stored metadata value. Invalid date values must be corrected to an ISO-style date or datetime.

If an action did not run, use dry-run first. Check lifecycle state, due date, skipped reason, unsupported action, calculation errors, missing target folder, manual enforcement enabled, confirm=true, allowed actions, and max action limits.

If scheduled enforcement is not running, check readiness blockers, scheduler enabled, scheduler dry-run setting, enforcement enabled, system service worker health, recent dry-run/manual enforcement events, and environment configuration.

If resolver trace is confusing, read the selected scope first, then the skipped candidates. Precedence is document, workflow template, folder, category, doc type, global.

Contact an administrator or support when permissions look correct but admin pages are hidden, a policy cannot be saved, workflow metadata cannot be resolved, scheduled readiness is blocked by system service configuration, or enforcement results conflict with dry-run evidence.