{"version":"2.1.248","anchor":"logger-tracks-latest-marking-and-refusal-separately","canonical_anchor":"logger-tracks-latest-marking-and-refusal-separately","heading":"Logger tracks latest marking and refusal separately","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/logger-tracks-latest-marking-and-refusal-separately","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Logger tracks `latest` marking and refusal separately\n\nThe logger remembers a refused latest-pointer update separately so it stops retrying blindly.\n\n**What**\n\nThe single flag saying the `latest` log pointer had been updated is now two, one for marked and one for refused, so a permission failure is remembered distinctly from a success and not retried blindly.\n\n**Evidence**\n\n`latestRefused`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}