MS Flow - Pagination Error from today on all instances

[dxshyam]

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-48...' 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

[MartinHutchcpa]

This appears to be a new error that I am also experiencing.

Have you heard of a fix yet?

[JoAnneCharlotte]

I'm also getting this error

[FabrizioKarl]

Same here. Starting today we are receiving this error when trying to list records with the Common Data Service connector.

[LeePope]

I'm also getting this same error in the EMEA region.  My Flow is trying to call Dynamics 365 and retrieve a list of Active Cases.  It seems to retrieve the list of queues and queue items successfully, but fails with this one particular call.  

InvalidPageResponse. The response is not a valid paginated response. The specified nextLink https://flow-apim-europe-001-westeurope-01.azure-apim.net/apim/dynamicscrmonline <etc etc etc> is not a well formed URI.

[RomiArg]

Hi, dxshyam. Thanks for your post! I'm also getting the error in South America region, but I'm getting it since Tuesday afternoon (in two different flows). They are flows that were working correctly and just started working with errors. I created a ticket for support three days ago but the analyst didn't say anything related to a workaround or something. So, I'll keep waiting for the resolution. Regards.

[dxshyam]

No, not yet. I am still looking for a fix.

[Rashkae]

I also received this error on an excel flow that updates a SharePoint list on a scheduled basis. 

[Anonymous]

Same thing here, just suddenly flows that were working fine just started failing.

As soon as any of you guys find a resolution please let us know.

Thanks!

[HISD_JSO]

Getting the same issue with the Excel Online Connector. Pagination is essentially busted.

[Manc_Gurl]

I too am getting this error today, my flow was working fine last week.

[arizomo]

I also received this error on a flow that were working fine just started failing.

[Anonymous]

I removed pagination, and set the Threshold as 10000 and NOW ITS WORKING, I dont know if this is good for all of you guys but just in case you dont have a large amount of records you could try that. Of course I think if I have more than 10000 records then Ill be in trouble but if not I think you can try that just temporary while Microsoft says whats going on.

[HISD_JSO]

@Anonymous wrote:

I removed pagination, and set the Threshold as 10000 and NOW ITS WORKING, I dont know if this is good for all of you guys but just in case you dont have a large amount of records you could try that. Of course I think if I have more than 10000 records then Ill be in trouble but if not I think you can try that just temporary while Microsoft says whats going on.

This did not work for me. Unless there is something I am missing, If you disable the pagination, it pulls  a maximum  256 records no mater what. If the pagination is off, the threshold settings is not even saved and resets to empty as soon as you reload.

[dxshyam]

@aegt Just gave it a try, it is in progress. will post again after the process completes.

Max value of threshold is 100,000. after the current flow completes execution. I will run that again with a threshold of 100,000 and see how it behaves.

Thank you,

Shyam

[dxshyam]

@aegt, how many records were you having when it executed successfully for you?

My observation on setting Pagination to OFF and Threshold to 10,000 is that the flow ignored Pagination and Threshold, perfomed the flow with the default limit of 512 records.

Could you please confirm if you had more than 512 records processed?

Regards,

Shyam

[Anonymous]

Make sure it returns the records you expect, because on my case the threshold didnt matter, only returned 2048 (SQL sonnection). Probably it will work but just make sure it did return what you need

[HISD_JSO]

@dxshyam What connector are you are using? I am using the excel online connector and I only get 256 records.

[Manc_Gurl]

Same for me with pagination off and threshold set to 3000 it only returns 256 rows. I'm using Excel connector

[dxshyam]

I am using List Records for Common Data Service

Regards,

Shyam