Get-PnPSearchCrawlLog -ContentSource Sites -Filter $filte …
     |                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Error: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.. Make sure you are   
     | granted access to the crawl log via the SharePoint search admin center at
     | https://<tenant>-admin.sharepoint.com/_layouts/15/searchadmin/crawllogreadpermission.aspx

🚀 Kudos to Kinga Kazala for contributing a valuable enhancement to #PnPPowerShell by adding the -IncreaseRequestTimeout parameter to the Get-PnPSearchCrawlLog cmdlet.

This improvement helps address the common timeout error: “The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.”

The new parameter extends the request timeout, allowing the call to run for up to 3 minutes. As noted in the documentation: “Increases the request timeout allowing the call to last up to 3 minutes. The ClientRuntimeContext enforces a three-minute limit; when increasing the timeout to its maximum of three minutes, this threshold may still be exceeded.” In my testing, I was able to successfully run Get-PnPSearchCrawlLog with a rowlimit parameter set to more than 300k records, which previously would have been challenging due to timeout constraints. These types of community driven contributions make a real difference when working with large scale SharePoint environments and troubleshooting search related issues. Learn more about the cmdlet here: 🔗 https://lnkd.in/es66th2N

#SharePoint #Microsoft365 #PnPPowerShell #PowerShell #M365 #OpenSource #CommunityContributions #Search #SharePointAdmin