Yesterday I was using the PnP Provisioning Engine to deploy a SharePoint Designer workflow and I got the following error:
[ERROR] Apply-SPOProvisioningTemplate : System.TimeoutException: The HTTP request has timed out
[ERROR] after 200000 milliseconds. —> System.Net.WebException: The request was aborted: The
[ERROR] request was canceled.
[ERROR] at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
[ERROR] at Microsoft.Workflow.Client.HttpGetResponseAsyncResult`1.OnGotResponse(IAsyncResult
I had seen this before in on-premises SharePoint 2013 farms.
So I need to start some services. Ai, I am on office 365. What should I do?
I went to my Office 365 admin -> SERVICE HEALTH -> Service Health and in the SharePoint Features I found an issue.
Current Status: Engineers are investigating an issue in which affected users are unable to publish workflows when using SharePoint Designer 2013. The investigation is currently focused on recent updates to the environment.
User Impact: Affected users are unable to publish workflows when using SharePoint Designer 2013. Users may encounter an error message which states, “Errors were found when compiling the workflow. The workflow files were saved but cannot be run.” SharePoint Designer 2010 is not impacted by this issue.
Scope of Impact: A very limited number of customers and users appear to be impacted. Engineers have received a few isolated customer reports of this issue.
Ah that is good someone has found an issue before I have reported it.
A couple of hours later and my workflows published without any problem.
Discover more from SharePains
Subscribe to get the latest posts sent to your email.
Pieter Veenstra
Is your business still running on paper trails, sprawling Excel files, or ageing Access databases? There's a better way — and I can show you exactly what it looks like. I'm the Technical Director of Vantage 365, a Microsoft solutions consultancy working with clients across the UK, the Netherlands, and worldwide. For over 30 years I've been turning messy, manual business processes into clean, automated systems that save time, reduce errors, and give teams the visibility they need to make better decisions. SharePains is not just any blog run by a Microsoft MVP. Have you ever used Try-Catch in Power Automate? The original post about Try-Catch in Power Automate can still be found on this site, https://sharepains.com/2018/02/07/try-catch-finally-in-power-automate-flow/ Or have you ever used the Pieter’s method to avoid variables and speed up your flows? https://sharepains.com/2020/03/11/pieters-method-for-advanced-in-flows/ You can contact me using contact@sharepains.com