{"version":"2.1.247","anchor":"workflow-failures-recorded-through-one-function","canonical_anchor":"workflow-failures-recorded-through-one-function","heading":"Workflow failures recorded through one function","tier":"internal","area":"Workflows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/workflow-failures-recorded-through-one-function","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Workflow failures recorded through one function\n\nWorkflow failures are now recorded in one place, so logging decisions are consistent.\n\n**What**\n\nSafety-classifier blocks, agent API errors, per-slot parallel and pipeline failures and auto-mode warnings all previously pushed a message onto a list and separately emitted a workflow log event at eight call sites. They now go through a single recorder with an explicit logging option, so what appears in the workflow log is decided in one place. The messages themselves are unchanged.\n\n**Evidence**\n\n`recordFailure: (ue) => E(ue, { log: !1 }),`\n\n- Area: Workflows\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}