{"version":"2.1.238","anchor":"a-second-status-line-can-report-its-own-errors","canonical_anchor":"a-second-status-line-can-report-its-own-errors","heading":"A second status line can report its own errors","tier":"notice","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/a-second-status-line-can-report-its-own-errors","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### A second status line can report its own errors\n\nIf you configure a second status line, it can now report its own errors instead of staying silent.\n\n**What**\n\nThe \"already logged once\" latches for status-line command failures moved from being shared across the whole process to being tracked per status line, so a second configured status line can still report its own success or `exec_error` instead of being silenced by the first one.\n\n**Evidence**\n\n`Status hook failed: `\n\n- Area: Terminal UI\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}