{"version":"2.1.232","anchor":"starting-a-new-goal-now-clears-the-old-one-explicitly","canonical_anchor":"starting-a-new-goal-now-clears-the-old-one-explicitly","heading":"Starting a new goal now clears the old one explicitly","tier":"internal","area":"Goals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/starting-a-new-goal-now-clears-the-old-one-explicitly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Starting a new goal now clears the old one explicitly\n\nReplacing a live goal now clears the old one and records why it ended.\n\n**What**\n\nWhen a new goal replaces one that is still live, the old goal is now cleared as a distinct step rather than dropped silently, and a new event records why a goal ended along with how many iterations it ran, how long it lasted and where it came from.\n\n**Details**\n\n- Recorded reasons in this build: `superseded` (a new goal replaces a live one), `user_clear`, `resume_swap` and `session_clear`.\n- The `superseded` case is the new behaviour; the rest describe clears that already happened.\n\n**Evidence**\n\n`tengu_goal_cleared`\n\n- Area: Goals\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}