{"version":"2.1.227","anchor":"cleanup-throttle-marker-self-heals-when-it-is-not-a-regular-","canonical_anchor":"cleanup-throttle-marker-self-heals-when-it-is-not-a-regular-","heading":"Cleanup throttle marker self-heals when it is not a regular file","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/cleanup-throttle-marker-self-heals-when-it-is-not-a-regular-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Cleanup throttle marker self-heals when it is not a regular file\n\nIf the cleanup marker file is a directory or symlink loop, it's deleted and rebuilt.\n\n**What**\n\nBefore trusting the `.last-cleanup` marker that rate-limits cleanup runs, the code inspects it. If the check fails with a symlink loop, directory or device-node error, it records a telemetry event with the error code and verdict, deletes the marker, and logs whether removal succeeded. A separate pass deletes stale files matching a fixed list of cleanup marker names.\n\n**Evidence**\n\n`tengu_cleanup_throttle_marker`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}