Intermittent “nextPageToken invalid or expired” error when Boomi process calls Jira REST API

[Senthilkumar Annamalai]

Intermittent “nextPageToken invalid or expired” error when Boomi process calls Jira REST API using HTTP connector.
The issue occurs randomly during pagination when Boomi retrieves multiple pages of results using the nextPageToken parameter.

Jira API responds with HTTP 400 Bad Request and the above error message.

In few other runs, the pagination completes successfully and all pages are retrieved without error.

The error is not reproducible consistently — it appears intermittently.

To isolate the issue, I tried in Postman. The same iterative API call is working as expected in Postman.

Boomi integration process that consumes the Jira Cloud REST API endpoint
https://xyz.atlassian.net/rest/api/3/search/jql?jql=project=BA%20AND%20updated%3E%222025-01-01%2001%3A12%22%20AND%20updated%3C%222025-10-08%2018%3A51%22&fields=*all,-comment&maxResults=200&nextPageToken=

Please give me some insight into how to fix this issue.

[Tuncay Senturk _Snapbytes_]

Hi @Senthilkumar Annamalai 

Welcome to the Community!

You're running into the quirks of Jira Cloud’s new search with pagination. 

- Make sure that for the first page call nextPageToken must be null, otherwise it returns 400. 

- Each nextPageToken is one-time use, make sure you are not using the same token.

- Tokens are tied to the same query, changing the query (e.g. adding some fields to the query params) might make the token invalid.

- If Boomi calls multiple page requests concurrently or retries while another branch is calling, the sequence breaks.

Other than that, it should not return 400. However, in the first days after they removed the old endpoint, this search used to return 400, and I had to improve the code to try again. I am not sure if it is still getting those 400s anymore.