Compute VM recovery points changed regions behaves in-consistently

We are using Nutanix Data protection APIs to compute the changed regions between VM recovery points, where we are seeing in-consistent behaviour. 

API version - v4.1

API 

1. First we do discover cluster on Prism central IP - /api/dataprotection/v4.1/config/recovery-points/{extId}/$actions/discover-cluster
2. Then we Compute VM change regions on Prism Element IP - api/dataprotection/v4.1/content/recovery-points/{recoveryPointExtId}/vm-recovery-points/{vmRecoveryPointExtId}/disk-recovery-points/{extId}/$actions/compute-changed-regions

So for Second request the start offset is provided as 0 to compute the regions from the start. It provides the change regions and let’s say the last offset changed is n. Now when we request the same compute regions API with the start offset n, it stills gives more compute regions which should not be the case as the last request ended the compute regions in n. 

We check below meta data response for if the response in paginated - 

1. isPaginated - flag

2. nextOffset - extraInfo

But still it doesn’t give paginated response and when call again provide more compute regions. Can someone please help us how to handle the pagination and getting all the compute regions in one API request?

Thanks