{"id":"6a727c07f864d49f3ec4a902","title":"2026 08 05 Build 811","path":"how-to/committee/release-notes/2026-08-05-build-811","contentMarkdown":"# 05-Aug-2026 — centralise Brevo report day ranges on one UTC-safe clamp [ref #279](https://github.com/nbarrett/ngx-ramblers/issues/279)\n\n## [build 811](https://github.com/nbarrett/ngx-ramblers/actions/runs/30961042987) — [commit c66f7e4](https://github.com/nbarrett/ngx-ramblers/commit/c66f7e482ee20576a5f948de40786069fc2ebda1)\n\n_____\n\n## What's new\n\nBrevo day ranges are handled in one shared place again. Nothing on the server or Mail Reports can ask Brevo for a calendar day after UTC today, which stops the early-UK-morning \"Start/End date should not be greater than current date\" failure.\n\n## At a glance\n\n- Mail Reports range controls and API calls stay aligned on UTC-safe days\n- Campaign reports, transactional reports, contact events, contact stats and unsubscribes all use the same clamp\n- Partial ranges (end-only) are capped as well as full start/end pairs","contentHtml":"<h1>05-Aug-2026 — centralise Brevo report day ranges on one UTC-safe clamp <a href=\"https://github.com/nbarrett/ngx-ramblers/issues/279\">ref #279</a></h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/30961042987\">build 811</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/c66f7e482ee20576a5f948de40786069fc2ebda1\">commit c66f7e4</a></h2>\n<hr>\n<h2>What&#39;s new</h2>\n<p>Brevo day ranges are handled in one shared place again. Nothing on the server or Mail Reports can ask Brevo for a calendar day after UTC today, which stops the early-UK-morning &quot;Start/End date should not be greater than current date&quot; failure.</p>\n<h2>At a glance</h2>\n<ul>\n<li>Mail Reports range controls and API calls stay aligned on UTC-safe days</li>\n<li>Campaign reports, transactional reports, contact events, contact stats and unsubscribes all use the same clamp</li>\n<li>Partial ranges (end-only) are capped as well as full start/end pairs</li>\n</ul>\n"}