Greetings!
We created a flow to deactivate all contacts on a specific date which is read from a custom entity (this entity contains only one record).
We have around 6500 contacts, since by default only 512 records were being processed, we set the Pagination On and Threshold as 10000. This resolved our problem and were able to successfully deactivate, activate all records several times.
Today when we tried we were getting Pagination Error, I am getting this in two of my trial accounts as well as my licensed instance
InvalidPageResponse. The response is not a valid paginated response. The specified nextLink 'https://unitedstates-002.azure-apim.net/apim/commondataservice/shared-commondataser-1ed6529d-d7b5-484a-9acd-49889550acb6/v2/datasets/orgd51ed6c0.crm/tables/contacts/items?%24filter=statecode+eq+0&%24skiptoken=%3ccookie+pagenumber%3d%222%22+pagingcookie%3d%22%253ccookie%2520page%253d%25221%2522%253e%253ccontactid%2520last%253d%2522%257b400A7204-98FD-E911-A815-000D3A35B658%257d%2522%2520first%253d%2522%257b42067204-98FD-E911-A815-000D3A35B658%257d%2522%2520%252f%253e%253c%252fcookie%253e%22+istracking%3d%22False%22+%2f%3e' is not a well formed URI.
Any idea why I am getting this error today? How to fix this? Is there any issue Azure today?
Below are the snap shots
Expanding Recurrence
Expanding List Records and its settings. Here we are reading a custom entity 'Deactivation date' which contains only one record. This record holds the date when all Contacts should be deactivated.
Expanding Apply to Each 3. Here in condition2, we check if current date is equal to deactivation date and if true using List records2 we filter all Active Contacts
In List Records 2 we filter for Active Contacts, in settings we have kept Pagination On and Threshold as 10000
In apply each, we are setting the status to Inactive
The flow fails by giving pagination error
Zooming the error message
Thanks,
Shyam
