Hello,
I’m seeing a repeatable issue with Jira api endpoint:
GET /rest/api/3/search/jql
The initial request succeeds and returns results plus a nextPageToken. However, when I use that returned token in the next request, Jira returns:
HTTP 404
{
"errorMessages": [
"Issue does not exist or you do not have permission to see it."
],
"errors": {}
}
The JQL itself is valid and runs successfully in Jira’s UI under the same user account. The query returns several thousand issues. Further, my PowerBi dashboard has been successfully working for months and just started erroring out (nothing changed on my end).
Additional details:
- Jira Cloud REST API v3
- Endpoint:
/rest/api/3/search/jql - Authentication: Basic authentication using Atlassian account email + API token is a standard token without scopes
- First API request succeeds
nextPageToken is returned by Jira- Subsequent request using that exact token returns the 404 above
- The failure occurs during pagination, not on the initial request
- I can run the JQL successfully in the Jira UI under the same user account
- This is being called from Power BI using
Web.Contents, but the Jira response body itself is the 404 shown above
My understanding is that Jira search should only return issues the authenticated user is permitted to browse, rather than failing the entire paginated search because of an inaccessible issue.
Has anyone seen /rest/api/3/search/jql return this 404 specifically when following a valid nextPageToken?
I’m trying to determine whether this is:
- a known issue with enhanced JQL pagination /
nextPageToken, - a permissions or issue-security edge case,
- or some other requirement for continuation requests that I’m missing.
Any guidance on how to identify which issue/project or pagination boundary is triggering the 404 would be greatly appreciated.