The question of this post is if others experience the same behavior. Maybe it’s only a fyi. Not sure if there is a solution to this rather than Atlassian fixing stuff in the backend.
In rare cases, the following v2 REST endpoint fails with status code 500 (internal server error):
api/v2/pages/1237975321?include-labels=true&include-version=true&include-versions=true&body-format=storage
The goal of this call is to get, well, the labels, versioning information and body in storage format of a page in a single call.
For about 1 in ~300 pages above call fails with this response:
{
"errors": [
{
"status": 500,
"code": "INTERNAL_SERVER_ERROR",
"title": "Internal Server Error",
"detail": null
}
]
}
But there is a workaround.
The workaround is to get metadata and body separately, like so:
Call 1 to get metadata: api/v2/pages/1237975321?include-labels=true&include-version=true&include-versions=true
Call 2 to get the body: api/v2/pages/1237975321?body-format=storage
This works for the affected pages.
The pages in question have been migrated from Confluence on-premises to the cloud, which might play a role. But then, the majority of those pages is fine.
Did anybody else experience this behavior?