{"version":"2.1.269","anchor":"async-repl-dispatch-queue-depth-check-unaffected-in-behaviou","canonical_anchor":"async-repl-dispatch-queue-depth-check-unaffected-in-behaviou","heading":"Async REPL dispatch queue depth check unaffected in behaviour but relocated","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/async-repl-dispatch-queue-depth-check-unaffected-in-behaviou","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Async REPL dispatch queue depth check unaffected in behaviour but relocated\n\nAsync REPL's queue-depth limit logic moved to a new internal function, same behavior\n\n**What**\n\nThe check that rejects a new asynchronous REPL (code execution) request when too many evaluations are already queued or running, along with its \"async REPL dispatch rejected\" message, was moved into a new internal function that is now invoked through the `call.runEngine` execution path. The wording and the logic itself are unchanged.\n\n**Why**\n\nThis is a code relocation tied to the broader REPL tool restructuring in this release, with no change in behavior: the same queue-depth limit still applies.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}