Not sure why you’d get that in your case when the total number of records isn’t a multiple of the paging count. I realized there is a condition where that original paging would have an issue so I shifted to utilizing the metadata of the profiles query instead to use the total count as the terminate condition. This might give some better results and not have the issue of hitting the no profiles found condition.
The context url: /profiles?metadata=true&profile_type_id=de5cb47c-2fcf-4eb5-8bcf-0316ffd563db&limit=100&offset=0
$sysparm_final$ = $response._metadata.limit$ + $response._metadata.offset$
TERMINATE_IF $sysparm_final$ == $response._metadata.total$
$sysparm_offset$ = $response._metadata.limit$ + $response._metadata.offset$
$endpoint.fullUrl$ = $application.baseUrl$ + "/profiles?metadata=true&profile_type_id=de5cb47c-2fcf-4eb5-8bcf-0316ffd563db&limit=" + $response._metadata.limit$ + "&offset=" + $sysparm_offset$