# Reliability and fixes

By Steven Van · 2026-07-08

The client now automatically retries service\_overload (HTTP 529) responses, respecting the Retry-After header as described in Request limits.

The [Notion](<https://creatorstoolbox.com/tools/notion>) API client now retries HTTP 529 service\_overload responses automatically, respecting the Retry-After header rather than failing immediately. The fix was contributed by community member @RyanBillard.

- Search's relevance sort now has the correct type, { property: "relevance" }.

- Pagination parameters accept start\_cursor: null, so a response's next\_cursor can be passed straight through without a null check.

Full details are in the [changelog entry](<https://developers.notion.com/page/changelog#july-8-2026>).

[![](<https://notion-demo.mintlify.app/images/og-image.png>)](<https://developers.notion.com/page/changelog#july-8-2026>)

![Notion](<https://www.google.com/s2/favicons?domain=notion.so&sz=128>)

Notion

All-in-one workspace for notes, docs, projects, and wikis — with AI built in for writing, summarizing, and organizing.

[View Notion →](<https://creatorstoolbox.com/tools/notion>)

Sources

[Original source](<https://developers.notion.com/page/changelog#july-8-2026>)

[Read Reliability and fixes on Creators Toolbox](<https://creatorstoolbox.com/blog/notion-reliability-and-fixes>)

---
Canonical source: https://creatorstoolbox.com/blog/notion-reliability-and-fixes