{"version":"2.1.248","anchor":"clearer-error-when-a-replayed-repl-run-outruns-its-cached-to","canonical_anchor":"clearer-error-when-a-replayed-repl-run-outruns-its-cached-to","heading":"Clearer error when a replayed REPL run outruns its cached tool calls","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/clearer-error-when-a-replayed-repl-run-outruns-its-cached-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Clearer error when a replayed REPL run outruns its cached tool calls\n\nReplayed REPL runs that make extra tool calls now fail with a clear nondeterminism error.\n\n**What**\n\nReplaying REPL code that makes more tool calls than the original run recorded now fails with a `ReplayCacheExhausted` error that points at nondeterminism as the likely cause.\n\n**Details**\n\n- The message names `Date.now` and `Math.random` as typical culprits for taking a different branch on replay.\n\n**Evidence**\n\n`likely nondeterminism (Date.now, Math.random) took a different branch.`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}