Sharepoint 2010 Workflow can no longer be published on Sharepoint 2013 for our Online site

Hi DenisCheong , we have the same issue.

the time it takes to solve this problem seems fatal to me

The last update:

Title: Workflows 2010 issue User Impact:

Users may be unable to create new or edit existing workflows under Workflows 2010.

More info: Users may receive the error(s): "Unexpected error on server associating the workflow," and "Errors were found when compiling the workflow. The Workflow files were saved but cannot run."

Users will experience relief as the activity progresses within the environment.

Current status: We've validated that the deployment is now progressing as expected and we’re monitoring its status to ensure it completes successfully.

Scope of impact: This issue may potentially affect any of your users attempting to create new or edit existing workflows within SharePoint Designer 2013, under Workflows 2010.

Start time: Tuesday, November 5, 2019, 9:23 AM (2:23 PM UTC)

Root cause: Our analysis identified that the infrastructure responsible for Workflows 2010 functionality contained a misconfiguration.

Next update by: Monday, November 11, 2019, 3:30 PM (8:30 PM UTC)

Hi DenisCheong  - We have a message in our Service Health Dashboard:

Dahai Fang 

we´ve managed to publish our workflow, and are now conducting functionality tests Before Rolling them out again. Man, this was one for the books.. 

Dahai FangThe link that I posted above is the only place I have found where the issue and resolution details are publicly available (and it is live updated each day).  Current status (unchanged since Saturday):

######################################## Mar 18, 2019 05:27 PM UTC ########################################
Title: Unable to edit existing workflows or create new workflows

User Impact: Users are unable to edit workflows or create new workflows in SharePoint 2010 using Designer and other protocols.

More info: Users may receive the error: "Unexpected error on server associating the workflow," and "Errors were found when compiling the workflow. The Workflow files were saved but cannot run."

As a result of this problem, you may be unable to execute the following tasks:
- Activating features that contain out-of-the-box or custom 2010 workflows
- Provisioning out-of-the-box or custom site templates that contain 2010 workflows

Additionally, attempting to edit existing workflows may cause those workflows to become dissociated with their SharePoint list. We've developed a fix for this issue and are preparing to apply it across the affected environment. Affected customers are encouraged to refrain from attempting to edit existing workflows until our fix is deployed.

Current status: We successfully deployed the fix to a test environment and have validated that our solution is effective. We're proceeding with deployment to the affected environment and are on track to complete this process by Saturday, March 23, 2019.

Scope of impact: Impact is specific to SharePoint 2010 workflows. Any user attempting to edit existing workflows or create new workflows may be affected by this event.

Estimated time to resolve: Based on current deployment progress, we expect this problem to be resolved by Saturday, March 23, 2019.

Next update by: Wednesday, March 20, 2019, at 8:00 PM UTC

SlavaGorbunovIt's pretty abysmal to see that:

1. It's taking Microsoft TWO WEEKS to resolve this issue, even though they already have the fix after one (which in of itself is too long).

2. Microsoft are still only treating this as a "business day" priority - no updates to the record over the weekend, not important enough for 24x7 support?

I'm presuming that it didn't take them two weeks to break it in the first place, and it was their own change which caused it (which clearly means they have inadequate testing in place), and also ... if their own changed caused it, then why did they have no backout plan to roll back their change?

So much for agile.

My team/organization is in the same boat as you...we just discovered this issue yesterday. This morning, we had a crucial business demonstration for a solution that leverages SPD2010 workflows due to the limitations of creating Document Sets within SPD2013. Luckily for us...we did not edit the previously published workflow to create Document Sets...no there was no issue with republishing. However, many other workflows for the same solution had to be re-written using SPD2013...took my team member literally all of yesterday and into the hours of early today to get the solution to a place where we could demonstrate functionality. 

I've alerted my organizations regarding the issue at hand...hoping people are not foolish enough to go and edit their existing/published workflows in SPD2010.

Also disappointed with the management of this issue. I do have access to the Health Service for our tenant and there is nothing posted about this incident. Being unaware of the current situation, we tried to publish updates to several SP2010 workflows, which are now broken.

Feels very much like Microsoft is trying to hide this issue, which is having a huge impact on many businesses. And we do still need SP2010 workflows since both Flow and SP2013 are lacking some of the same functionality. 

It's actually worse for us - I have broken a business critical workflow by attempting to publish an updated version of it last week - due to the outage it is now no longer associated to the list, and cannot be run (it just gives a blank page with a "\" at the top of it).