{"version":"2.1.250","anchor":"wrong-value-reported-when-arming-a-live-subscription-failed","canonical_anchor":"wrong-value-reported-when-arming-a-live-subscription-failed","heading":"Wrong value reported when arming a live subscription failed","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.250\/e\/wrong-value-reported-when-arming-a-live-subscription-failed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.250","markdown":"### Wrong value reported when arming a live subscription failed\n\nWhen a live subscription fails to start, the error you see is now the actual failure.\n\n**What**\n\nAn error handler in the live-subscription arming path reported an outer captured value instead of the exception it had just caught, so the real error was lost. It now passes the caught error.\n\n**Evidence**\n\n`armLiveSubscription: late-park fall-through lost its park`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}