Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[BUG]: Error importing new CrisisCommunicationNewsNotification.zip - Pagination Policy issue
See original GitHub issueDescribe the bug When importing the new (2020.03.23) version of CrisisCommunicationNewsNotification.zip into Flow, getting an error message and the Flow fails to import. No option to fix this from the UI.
To Reproduce Steps to reproduce the behavior:
- Download the 2020.03.23 CrisisCommunicationPackage.zip
- Extract
CrisisCommunicationNewsNotification.zipfrom the Package .zip - Go to https://flow.microsoft.com/
- Click on ‘My Flows’
- Click on ‘Import’
- Click on ‘Upload’ and browse to the extracted
CrisisCommunicationNewsNotification.zip - Authenticate the Connections (“Select during import” etc.)
- Click on ‘Import’
- Get the error message:
The pagination policy of workflow run action ‘Get_group_members’ of type ‘ApiConnection’ at line ‘1’ and column ‘5770’ is not valid. The value specified for property ‘minimumItemsCount’ exceeds the maximum allowed. Actual: ‘100000’. Maximum: ‘5000’.
Expected behavior Import should complete without errors.
Screenshots
If applicable, add screenshots to help explain your problem.
Interface(please complete the following information):
- Browser: Chrome
Additional context
Manually editing definition.json within the .zip file, changing 100,000 to 1,000 then reconstructing the .zip file and importing that works OK.
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thank you @davidMbrooke for reporting this. We have updated the solution to fix this issue, and updates to the documentation will be published later today.
That’s what I figured as the underlying issue; thanks. Since the Import doesn’t complete I don’t get any opportunity to Export.
As I noted at the bottom of my original post, I’ve been able to work around this issue by unpacking the .zip and hand-editing
definition.jsonto reduce the limit as you describe - then reconstructing the .zip and importing as normal.Not everyone will be comfortable doing that though, so would be good if you could fix for the next release of the Package.