-
Notifications
You must be signed in to change notification settings - Fork 336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Get-PnPFlow Times Out after 100 Seconds #3794
Comments
It appears that this was previously raised as a discussion here: #1871 |
I too am seeing the same error when when running Get-PnPFlow in a windows terminal, PS7 prompt, version 2.3.66 |
I opened a PR at #3820 to fix the issue, if you want to give it a try. |
Should be fixed with tomorrow’s nightly builds . |
Hello -- I was able to install the pre-release locally (on my machine) and it did appear to fix the issue -- Thank You! However, I have a question (a couple actually):
Thanks |
For what it's worth, I figured it out (maybe this will help someone else in a similar situation). I installed the needed (updated) module locally on my laptop under PowerShell v7. Once installed, I found the module locally under C:\Users\UserName\Documents\PowerShell\Modules\PnP.PowerShell. I then zipped that folder using the same file name as the module name. Then I removed the previous version of the module from my Azure Runbook modules and replaced it by importing the ZIP file I created as the replacement for PnP.PowerShell. Now I am able to run my runbook without encountering the 100s HTTP timeout error. |
Reporting an Issue or Missing Feature
Get-PnPFlow cmdlet times out after 100 seconds.
Expected behavior
The command should return a list of Power Automate flows from the tenant.
Actual behavior
Issue occurred on multiple environments, with and without the -AsAdmin switch passed.
![image](https://private-user-images.githubusercontent.com/139259660/308270119-433e6909-5884-4abb-bc61-914d2e313e9a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ3Njg1NDcsIm5iZiI6MTcyNDc2ODI0NywicGF0aCI6Ii8xMzkyNTk2NjAvMzA4MjcwMTE5LTQzM2U2OTA5LTU4ODQtNGFiYi1iYzYxLTkxNGQyZTMxM2U5YS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODI3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgyN1QxNDE3MjdaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT00ZDdiODM4YWEwZTBhNjQ3MTMxOTA5OWEzZjgxNzI0N2EyZDY5ZGZlYWRhYTBmODJlNmEzNzQ4OTQzZDk3MTNjJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.AkjkzPPsjcHeoTYJN_RKGY4b08waUuCkKZC5IZilqqk)
Steps to reproduce behavior
Connect-PnPOnline -Url $spAdminUrl -Interactive
Get-PnPFlow
Get-PnPFlow -AsAdmin
What is the version of the Cmdlet module you are running?
2.3.69 (updated after experiencing this bug
Which operating system/environment are you running PnP PowerShell on?
The text was updated successfully, but these errors were encountered: