Essentially, this appears to be the fault of the API, whilst advertised to return 100 items per page, this isn't always the case when calling the API (via cURL / Insomnia) on odd occasions it returns less, even though this isn't the end of the required item count:
Calls to obtain page 0 of tasks for my specific team id, returned task counts:
100, 100, 95, 100, 100, 100, 100, 100, 100, 100, 83, 100, 100, 100, 100, 100, 100, 100...
In the event of hitting less than 100 items, the current plugin code will exit querying for more pages (as it assumes this was the last page as it wasn't wrt the docs a full 100 item page).
Unfortunately the API doesn't return any headers or payload data which would indicates if there is a next page to obtain.
Potential solution for this would be to keep fetching pages until 0 items is returned (will fire off 1 more request than required, which could be frustrating on a low rate-limit band) - could have potential negative delay if the last useful page was obtained on last usage per rate limit and had to wait for the back off just to get an empty page...