Azure LP patterns fails orchestration when the number of records returned is equal to the multiple of the page sizes (default 100)DescriptionThe paginated execution of API is decided based on the number of resources returned in a single page and is performed based on the presence of an attribute in the API response indicating whether there is a next page. If the total number of resources can be divided by the page size (default 100), then the last page would contain all the last records, leaving 0 records to be fetched in a next page. Normally, this should mean that there is no need for a next page. However, in Azure this is not the case and their API response contains URL for a next page that would hold 0 records. This causes a processing problem because patterns have a limitation and need to populate their main CI table. But this cannot happen if there are no records in the API response, which causes the last page being processed to gracefully exit with no records found. If this page is the last to be processed during discovery, this would break the Orchestrator process and will stop any following patterns from being triggered, because the engine "thinks" that there is a problem with the execution.Steps to Reproduce 1. Select an Azure master service account. 2. Set the pattern page size to a number so that MOD/page size returns zero.3. Schedule and run discovery and check the log. Result - the last page of the Sub Account pattern would gracefully exit and if this page is the last one being processed, it would stop discovery.WorkaroundManually modify the page size for the problematic Pattern and its API call from: "{\"query\": \"resourcecontainers |where type == 'microsoft.resources/subscriptions' \", \"managementGroups\": [\"" + $service_account[1].object_id + "\"], \"options\": {\"$top\": 100}}" To "{\"query\": \"resourcecontainers |where type == 'microsoft.resources/subscriptions' \", \"managementGroups\": [\"" + $service_account[1].object_id + "\"], \"options\": {\"$top\": 99}}"Related Problem: PRB1662592