{"version":"2.1.227","anchor":"background-jobs-daemon-markers-and-insights-caches-use-stora","canonical_anchor":"background-jobs-daemon-markers-and-insights-caches-use-stora","heading":"Background jobs, daemon markers and insights caches use storage keys","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/background-jobs-daemon-markers-and-insights-caches-use-stora","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Background jobs, daemon markers and insights caches use storage keys\n\nBackground job files, daemon markers and insight caches can live in the storage layer instead of on disk.\n\n**What**\n\nBackground job teardown deletes the job's storage scope rather than removing its directory, daemon host-managed markers and pty pid files are written and deleted as storage keys, and the usage-insights caches are read in batches with a per-key fallback. Each keeps the old filesystem path when the newer storage backend is not present.\n\n**Evidence**\n\n`host-managed`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}