{"id":"6a313c578cee56d0d71bb214","title":"2026 06 16 Other","path":"how-to/committee/release-notes/2026-06-16-other","contentMarkdown":"# 16-Jun-2026 — show sync error detail instead of [object Object]\n\n## [build 699](https://github.com/nbarrett/ngx-ramblers/actions/runs/27615770048) — [commit 9f281dc](https://github.com/nbarrett/ngx-ramblers/commit/9f281dcc8af1950c9e6d76ad1abb925031842308)\n\n_____\n\nWhen a Salesforce sync fails (for example TOKEN_MISSING), the failure\nbanner rendered the error object directly, so it read \"Salesforce sync\nfailed: [object Object]\". The error is now passed through a small helper\nthat extracts errorMessage, message or errorCode (falling back to a JSON\nstring), so the banner shows the real detail. The precise message was\nalready visible in the audit-log table below the banner; this makes the\nbanner itself readable. Surfaced while testing the inbox work.","contentHtml":"<h1>16-Jun-2026 — show sync error detail instead of [object Object]</h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/27615770048\">build 699</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/9f281dcc8af1950c9e6d76ad1abb925031842308\">commit 9f281dc</a></h2>\n<hr>\n<p>When a Salesforce sync fails (for example TOKEN_MISSING), the failure\nbanner rendered the error object directly, so it read &quot;Salesforce sync\nfailed: [object Object]&quot;. The error is now passed through a small helper\nthat extracts errorMessage, message or errorCode (falling back to a JSON\nstring), so the banner shows the real detail. The precise message was\nalready visible in the audit-log table below the banner; this makes the\nbanner itself readable. Surfaced while testing the inbox work.</p>\n"}