{"version":"2.1.246","anchor":"command-queue-removals-carry-a-reason","canonical_anchor":"command-queue-removals-carry-a-reason","heading":"Command queue removals carry a reason","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/command-queue-removals-carry-a-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Command queue removals carry a reason\n\nDropped queued commands now record why they were removed instead of vanishing silently.\n\n**What**\n\nThe internal command queue's `remove`, `consume`, `removeByFilter` and `clearCommandQueue` now take a reason and forward it to the change listener, so dropped commands can be attributed instead of vanishing anonymously. A `getDrainableMainThreadQueueLength` accessor was added.\n\n**Evidence**\n\n`getDrainableMainThreadQueueLength`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}