{"version":"2.1.223","anchor":"api-error-metadata-is-recovered-from-wrapped-errors","canonical_anchor":"api-error-metadata-is-recovered-from-wrapped-errors","heading":"API error metadata is recovered from wrapped errors","tier":"notice","area":"Error Reporting","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/api-error-metadata-is-recovered-from-wrapped-errors","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### API error metadata is recovered from wrapped errors\n\nError reports now keep the status code and request id even when the error was wrapped.\n\n**What**\n\nStatus codes and request ids survive when an API error was rethrown inside another Error.\n\n**Details**\n\n- Error reporting unwraps `error.cause`.\n- If the cause is an API error, its status and request id populate `apiErrorStatus` and `requestId`.\n- Previously that metadata was lost for wrapped errors.\n\n**Evidence**\n\n`apiErrorStatus`\n\n- Area: Error Reporting\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}