{"version":"2.1.236","anchor":"oversized-published-pages-retry-without-block-ids","canonical_anchor":"oversized-published-pages-retry-without-block-ids","heading":"Oversized published pages retry without block ids","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/oversized-published-pages-retry-without-block-ids","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Oversized published pages retry without block ids\n\nA published page that is barely too big is retried without hidden markers instead of failing.\n\n**What**\n\nWhen a published artifact page exceeds its byte limit only because of the invisible per-block identifiers added during rendering, it is re-rendered once with those omitted and published again instead of failing.\n\n**Details**\n\n- The retry is unconditional inside the publish path and is recorded.\n- The too-large report now also carries how many bytes the block ids accounted for.\n\n**Evidence**\n\n`block_ids_over_cap`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}