Forum Discussion
Sharepoint 2010 Workflow can no longer be published on Sharepoint 2013 for our Online site
Our Service Health Dashboard has an entry for this:
SP175429 - Unable to edit existing workflows or create new workflows
- Nanovac_ABMar 12, 2019Copper Contributor
And not chasing Deleted - meerly venting frustation :)
- DenisCheongMar 12, 2019Brass ContributorDoes anybody following this thread have access to the Microsoft dashboard with the resolution status?
https://portal.office.com/AdminPortal/Home#/servicehealth- Ryan StoneMar 12, 2019Iron Contributor
No change in status that I can see. Still basically "we are working on it" and that's it.
- Nanovac_ABMar 12, 2019Copper Contributor
Hi Kelly,
i find it remarkable that this type of issue can occur. I Believe not only our business but many other is also getting damaged by this kind of outtage. We´ve got business critical processes that are at standstill, causing significant financial/business damage.
- DenisCheongMar 12, 2019Brass Contributor
Google has now indexed another page with more details on this outage:
https://answers.microsoft.com/en-us/msoffice/forum/all/unable-to-unpdate-workflow-in-sharepoint-designer/cacd70f9-2ed6-4db3-a55b-b9284251571e
- DenisCheongMar 12, 2019Brass Contributor
To his credit, I don't think that Deleted works for Microsoft, but he does have access to Microsoft's service health dashboard (which I don't have and they don't publish online that I know of).
It is very poor service and service integration that there can be a global outage of this, which has lasted so long (coming up to a week now) with neither a public disclosure nor a private disclosure that permeates down to me as a business user / site collection admin (which is a service management integration issue between my support organisation and Microsoft, which exists in most if not all of their large corporate customers).
I also still don't understand why there is still a core functionality gap between SharePoint 2010 workflows and their replacements (2013 workflows and Flow) which also means we can't avoid relying on them to function - and have no possible workaround during this outage.
- DenisCheongMar 12, 2019Brass Contributor
+1 can we please have an update on resolving this. I've spent half a day isolating the issue to "not me" and was fortunate enough to find this post through Google.
These types of major issues deserve broader visibility to the affected people. It first occurred on Friday last week.
- VasanthMuruganMar 12, 2019Copper Contributor
Hi Kelly
Do we have any updates to this issue? few workflows in our production system are impacted.