{"version":"2.1.223","anchor":"deep-link-registration-and-cleanup-sentinels-can-be-stored-a","canonical_anchor":"deep-link-registration-and-cleanup-sentinels-can-be-stored-a","heading":"Deep-link registration and cleanup sentinels can be stored as state keys","tier":"internal","area":"Storage Backend","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/deep-link-registration-and-cleanup-sentinels-can-be-stored-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Deep-link registration and cleanup sentinels can be stored as state keys\n\nSmall marker files for deep links and cleanup timing can now be kept as storage keys.\n\n**What**\n\nThe `.deep-link-register-failed` and `.last-cleanup` marker files now have storage-key equivalents.\n\n**Details**\n\n- freshness is checked with `stat` instead of a filesystem stat, and the markers are written and removed with `write`\/`delete`\n- a new error log fires when the cleanup stamp write fails\n\n**Evidence**\n\n`.last-cleanup write failed: `\n\n- Area: Storage Backend\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}