{"version":"2.1.251","anchor":"mock-replay-pins-a-capped-number-of-recorded-interactions","canonical_anchor":"mock-replay-pins-a-capped-number-of-recorded-interactions","heading":"Mock replay pins a capped number of recorded interactions","tier":"internal","area":"Plugin Eval","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/mock-replay-pins-a-capped-number-of-recorded-interactions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Mock replay pins a capped number of recorded interactions\n\nMock replay pins a capped number of recordings and warns you to prune unused ones.\n\n**What**\n\nThe internal eval mock-replay loader now pins only up to a fixed number of recorded interactions per file and warns to prune recordings no case still reaches once that cap is passed. The cap is an internal constant whose value is not visible in the build.\n\n**Evidence**\n\n`only the first ${oo} are pinned for replay \u2014 prune ones no case reaches any more`\n\n- Area: Plugin Eval\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}