# Page writes return 504 when a request times out

By Steven Van · 2026-09-24

A timed-out page write now gets its own 504 status instead of a generic 500, while writes that run out of time budget still return 503.

[Notion](<https://creatorstoolbox.com/tools/notion>)'s API now returns HTTP 504 gateway\_timeout when a page write runs past its deadline, instead of the HTTP 500 internal\_server\_error it returned before. This applies to updating a page's content as markdown and to the notion-update-page MCP tool; the notion-create-pages and notion-convert-page-to-skill MCP tools already returned 504 in this case.

A 504 does not mean the write was undone, so check whether the change was saved before retrying it. A write that runs out of its time budget still returns 503 service\_unavailable, with additional\_data.retry\_guidance on what to do next. See the [request limits](<https://developers.notion.com/reference/request-limits>) page for when to retry each status.

![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>)

[Read the original announcement →](<https://developers.notion.com/reference/request-limits>)

[Read Page writes return 504 when a request times out on Creators Toolbox](<https://creatorstoolbox.com/blog/notion-page-writes-return-504-when-a-request-times-out>)

---
Canonical source: https://creatorstoolbox.com/blog/notion-page-writes-return-504-when-a-request-times-out