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

%3CLINGO-SUB%20id%3D%22lingo-sub-364112%22%20slang%3D%22en-US%22%3ESharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364112%22%20slang%3D%22en-US%22%3E%3CP%3EDear%20all%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3Bwe%20run%20a%20SharePoint%20Online%20site%2C%20where%20we%20have%20a%20number%20of%20workflows%20(2010)%20running%20mainly%20to%20generate%20documents%20etc%20in%20our%20automated%20workflows.%20All%20has%20been%20working%20fine%2C%20till%20today%2C%20when%20we%20had%20some%20modifications%20we%20wanted%20to%20execute%20on%20some%20of%20the%202010%20workflows.%20We%20are%20using%20Sharepoint%20designer%202013.%20When%20saving%20the%20workflow%2C%20there%20are%20no%20issues%2C%20but%20when%20we%20try%20to%20publish%20we%20get%20an%20error%20(see%20attached)%20%5BUnexpected%20error%20on%20server%20associating%20the%20workflow%5D%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20584px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F86430i8885CEF032D64661%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Sk%C3%A4rmklipp%202019-03-11%2010.37.18.png%22%20title%3D%22Sk%C3%A4rmklipp%202019-03-11%2010.37.18.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3ERight%20now%2C%20we%C2%B4re%20at%20a%20standstill%2C%20and%20I%20can%20not%20find%20any%20real%20relevant%20information%20online%20on%20this.%20Some%20%22older%22%20stuff%20on%20temporary%20files%20etc%20have%20been%20reviewed%2C%20but%20without%20success.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPretty%20desperate%20now%20to%20get%20some%20help%20-%20Everything%20is%20much%20appreciated.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-364112%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-382905%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-382905%22%20slang%3D%22en-US%22%3EMe%20too!%20It%20was%20very%20hard%20to%20believe%20after%20such%20a%20LONG%20outage%20-%20two%20and%20a%20half%20weeks%20-%20which%20Microsoft%20is%20now%20calling%20an%20%22event%22%2C%20but%20my%20SharePoint%202010%20workflows%20are%20now%20publishing%20and%20look%20to%20be%20working!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-382704%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-382704%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F248866%22%20target%3D%22_blank%22%3E%40CindiCostello%3C%2FA%3E%26nbsp%3Bcan%20you%20please%20tell%20us%20what%20you%20have%20done%3F%20tnk!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-382654%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-382654%22%20slang%3D%22en-US%22%3E%3CP%3EWOO%20HOO!%26nbsp%3B%20We%20are%20finally%20up%20and%20running%20with%202010%20workflows%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-382620%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-382620%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F299104%22%20target%3D%22_blank%22%3E%40DenisCheong%3C%2FA%3E%26nbsp%3BI%20was%20able%20to%20create%20and%20publish%20a%20SP%202010%20workflow.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-382531%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-382531%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64401%22%20target%3D%22_blank%22%3E%40Dahai%20Fang%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ewe%C2%B4ve%20managed%20to%20publish%20our%20workflow%2C%20and%20are%20now%20conducting%20functionality%20tests%20Before%20Rolling%20them%20out%20again.%20Man%2C%20this%20was%20one%20for%20the%20books..%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-381772%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-381772%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F298574%22%20target%3D%22_blank%22%3E%40Nanovac_AB%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EWorks%20here%20now!%20Finally!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-381680%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-381680%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F166482%22%20target%3D%22_blank%22%3E%40Chih-Ang%20Lin%3C%2FA%3EThat's%20great%20to%20hear%20...%20it%20still%20doesn't%20work%20for%20us%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-381678%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-381678%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F299104%22%20target%3D%22_blank%22%3E%40DenisCheong%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIncredible...my%20eyes%20may%20be%20deceiving%20me%20but%20I%20believe%20the%20fix%20has%20been%20deployed%20to%20my%20tenant%2Fenvironment.%20I%20was%20able%20to%20edit%20and%20publish%20a%20SPD2010%20workflow!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-380066%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-380066%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F299104%22%20target%3D%22_blank%22%3E%40DenisCheong%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWas%20thrilled%20to%20see%20this%20blog.%26nbsp%3B%20We%20are%20having%20the%20same%20issue%20and%20as%20of%201%3A00%20PM%203%2F21%2F19%20-%20it%20has%20not%20been%20corrected.%26nbsp%3B%20I'll%20keep%20you%20posted%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-378168%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-378168%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F299104%22%20target%3D%22_blank%22%3E%40DenisCheong%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ei'll%20post%20an%20update%20here%20the%20minute%20our%20workflows%20can%20be%20deployed..%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-378165%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-378165%22%20slang%3D%22en-US%22%3ENeither%20me%20..%20but%20I%20guess%20we're%20almost%20there%20-%20only%20a%20couple%20of%20days%20before%20we've%20been%20promised%20a%20complete%20fix%20will%20be%20deployed.%3CBR%20%2F%3E%3CBR%20%2F%3EThey%20are%20now%20only%20doing%20status%20updates%20every%20two%20days%20(wtf%3F)%2C%20so%20I%20don't%20think%20we'll%20get%20an%20update%20tomorrow%20morning%20-%20it%20won't%20be%20until%20Saturday%20my%20time%20(UTC%2B11)%20that%20they%20post%20the%20next%20update.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-378151%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-378151%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F299104%22%20target%3D%22_blank%22%3E%40DenisCheong%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eit%C2%B4s%20still%20not%20functional%20on%20my%20end.%20Same%20errors%20as%20before.%26nbsp%3B%20%3A%5C%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-377980%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-377980%22%20slang%3D%22en-US%22%3ELatest%20update%20from%20Microsoft%20overnight%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%22Current%20status%3A%20The%20deployment%20of%20the%20fix%20is%20approximately%2017%20percent%20complete.%20We'll%20continue%20to%20monitor%20the%20environment%20as%20the%20deployment%20progresses%20to%20ensure%20that%20it%20completes%20as%20expected.%22%3CBR%20%2F%3E%3CBR%20%2F%3EI%20don't%20know%20whether%20this%20means%20that%20it's%20been%20deployed%20to%2017%25%20of%20the%20sites%20that%20they%20host%2C%20but%20that%20sounds%20plausible%20-%20meaning%20that%20the%20fix%20is%20gradually%20going%20live.%3CBR%20%2F%3E%3CBR%20%2F%3EIt's%20still%20not%20working%20on%20our%20site%2C%20but%20I%20would%20recommend%20that%20you%20build%20a%20test%20and%20see%20if%20you%20are%20lucky%20enough%20to%20have%20it%20working%20in%20yours.%20Create%20a%20new%20SharePoint%202010%20workflow%20against%20a%20list%2C%20leave%20it%20blank%20and%20try%20to%20publish%20it%20to%20see%20if%20it%20works.%20If%20it%20does%20work%2C%20please%20post%20back%20here%20as%20this%20is%20the%20only%20live%20thread%20about%20the%20issue%20that%20I'm%20aware%20of.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-376495%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-376495%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64401%22%20target%3D%22_blank%22%3E%40Dahai%20Fang%3C%2FA%3EThe%20link%20that%20I%20posted%20above%20is%20the%20only%20place%20I%20have%20found%20where%20the%20issue%20and%20resolution%20details%20are%20publicly%20available%20(and%20it%20is%20live%20updated%20each%20day).%26nbsp%3B%20Current%20status%20(unchanged%20since%20Saturday)%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3E%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%20Mar%2018%2C%202019%2005%3A27%20PM%20UTC%20%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%23%0ATitle%3A%20Unable%20to%20edit%20existing%20workflows%20or%20create%20new%20workflows%0A%0AUser%20Impact%3A%20Users%20are%20unable%20to%20edit%20workflows%20or%20create%20new%20workflows%20in%20SharePoint%202010%20using%20Designer%20and%20other%20protocols.%0A%0AMore%20info%3A%20Users%20may%20receive%20the%20error%3A%20%22Unexpected%20error%20on%20server%20associating%20the%20workflow%2C%22%20and%20%22Errors%20were%20found%20when%20compiling%20the%20workflow.%20The%20Workflow%20files%20were%20saved%20but%20cannot%20run.%22%0A%0AAs%20a%20result%20of%20this%20problem%2C%20you%20may%20be%20unable%20to%20execute%20the%20following%20tasks%3A%0A-%20Activating%20features%20that%20contain%20out-of-the-box%20or%20custom%202010%20workflows%0A-%20Provisioning%20out-of-the-box%20or%20custom%20site%20templates%20that%20contain%202010%20workflows%0A%0AAdditionally%2C%20attempting%20to%20edit%20existing%20workflows%20may%20cause%20those%20workflows%20to%20become%20dissociated%20with%20their%20SharePoint%20list.%20We've%20developed%20a%20fix%20for%20this%20issue%20and%20are%20preparing%20to%20apply%20it%20across%20the%20affected%20environment.%20Affected%20customers%20are%20encouraged%20to%20refrain%20from%20attempting%20to%20edit%20existing%20workflows%20until%20our%20fix%20is%20deployed.%0A%0ACurrent%20status%3A%20We%20successfully%20deployed%20the%20fix%20to%20a%20test%20environment%20and%20have%20validated%20that%20our%20solution%20is%20effective.%20We're%20proceeding%20with%20deployment%20to%20the%20affected%20environment%20and%20are%20on%20track%20to%20complete%20this%20process%20by%20Saturday%2C%20March%2023%2C%202019.%0A%0AScope%20of%20impact%3A%20Impact%20is%20specific%20to%20SharePoint%202010%20workflows.%20Any%20user%20attempting%20to%20edit%20existing%20workflows%20or%20create%20new%20workflows%20may%20be%20affected%20by%20this%20event.%0A%0AEstimated%20time%20to%20resolve%3A%20Based%20on%20current%20deployment%20progress%2C%20we%20expect%20this%20problem%20to%20be%20resolved%20by%20Saturday%2C%20March%2023%2C%202019.%0A%0ANext%20update%20by%3A%20Wednesday%2C%20March%2020%2C%202019%2C%20at%208%3A00%20PM%20UTC%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-376489%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-376489%22%20slang%3D%22en-US%22%3E%3CP%3EOK%2C%20the%20problem%20is%20still%20here.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20unbelievable!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-376007%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-376007%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F299104%22%20target%3D%22_blank%22%3E%40DenisCheong%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAgree%2C%20this%20has%20been%20extremely%20poorly%20managed%2C%20and%2C%20especially%20as%20some%20workflow%20functionality%20just%20does%20not%20operate%20on%20the%202013%20platform.%20This%20has%20definately%20been%20an%20event%20that%20has%20had%20tremendous%20impact%20on%20our%20business%2C%20and%20we%C2%B4re%20looking%20at%20alternative%20ways%20forward%2C%20as%20a%202%20week%20outtage%20with%20Little%2Fno%20information%20is%20just%20not%20acceptable.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-376001%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-376001%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F302470%22%20target%3D%22_blank%22%3E%40SlavaGorbunov%3C%2FA%3EIt's%20pretty%20abysmal%20to%20see%20that%3A%3C%2FP%3E%3CP%3E1.%20It's%20taking%20Microsoft%20TWO%20WEEKS%20to%20resolve%20this%20issue%2C%20even%20though%20they%20already%20have%20the%20fix%20after%20one%20(which%20in%20of%20itself%20is%20too%20long).%3C%2FP%3E%3CP%3E2.%20Microsoft%20are%20still%20only%20treating%20this%20as%20a%20%22business%20day%22%20priority%20-%20no%20updates%20to%20the%20record%20over%20the%20weekend%2C%20not%20important%20enough%20for%2024x7%20support%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20presuming%20that%20it%20didn't%20take%20them%20two%20weeks%20to%20break%20it%20in%20the%20first%20place%2C%20and%20it%20was%20their%20own%20change%20which%20caused%20it%20(which%20clearly%20means%20they%20have%20inadequate%20testing%20in%20place)%2C%20and%20also%20...%20if%20their%20own%20changed%20caused%20it%2C%20then%20why%20did%20they%20have%20no%20backout%20plan%20to%20roll%20back%20their%20change%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20much%20for%20agile.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-375996%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-375996%22%20slang%3D%22en-US%22%3E%3CP%3EAnother%20problem%20with%20the%20publishing%20workflow%20to%20Content%20Type%20is%20that%20after%20the%20error%20during%20publishing%20the%20Workflow%20Settings%20page%20of%20the%20Content%20Type%20also%20returns%20an%20error.%3C%2FP%3E%3CP%3EE.g.%20attached%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369787%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369787%22%20slang%3D%22en-US%22%3EGoogle%20has%20finally%20indexed%20some%20semi-useful%20info%20on%20the%20outage.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22http%3A%2F%2Fstatus.rutgers.edu%2FConnect-DEGRADED%2FSharePoint-DEGRADED%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fstatus.rutgers.edu%2FConnect-DEGRADED%2FSharePoint-DEGRADED%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369695%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369695%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20team%2Forganization%20is%20in%20the%20same%20boat%20as%20you...we%20just%20discovered%20this%20issue%20yesterday.%20This%20morning%2C%20we%20had%20a%20crucial%20business%20demonstration%20for%20a%20solution%20that%20leverages%20SPD2010%20workflows%20due%20to%20the%20limitations%20of%20creating%20Document%20Sets%20within%20SPD2013.%20Luckily%20for%20us...we%20did%20not%20edit%20the%20previously%20published%20workflow%20to%20create%20Document%20Sets...no%20there%20was%20no%20issue%20with%20republishing.%20However%2C%20many%20other%20workflows%20for%20the%20same%20solution%20had%20to%20be%20re-written%20using%20SPD2013...took%20my%20team%20member%20literally%20all%20of%20yesterday%20and%20into%20the%20hours%20of%20early%20today%20to%20get%20the%20solution%20to%20a%20place%20where%20we%20could%20demonstrate%20functionality.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20alerted%20my%20organizations%20regarding%20the%20issue%20at%20hand...hoping%20people%20are%20not%20foolish%20enough%20to%20go%20and%20edit%20their%20existing%2Fpublished%20workflows%20in%20SPD2010.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369383%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369383%22%20slang%3D%22en-US%22%3E%3CP%3EWell%20it's%20now%20officially%20a%20full%20week%20without%20this%20working%2C%20and%20we%20have%20...%20nothing.%26nbsp%3B%20No%20update%2C%20no%20ETR%2C%20just%20crickets%2C%20and%20nothing%20from%20my%20own%20organisation's%20%22support%22%20function.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20keen%20to%20understand%20how%20everyone%20else%20is%20dealing%20with%20the%20outage%2C%20what%20workarounds%20have%20you%20implemented%20-%20and%20how%20successful%20have%20they%20been%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhy%20are%20%3CEM%3Eyou%20%3C%2FEM%3Estill%20relying%20on%20SharePoint%202010%20workflows%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20us%20-%20these%20are%20all%20new%20workflows%20developed%20in%20the%20last%2012%20months%20that%20require%20functionality%20that%20is%20only%20available%20in%20SharePoint%202010%20workflows%20-%20creation%20of%20Document%20Sets%20(actually%20of%20content%20types%20%3CEM%3Ederived%20from%3C%2FEM%3E%20document%20sets%2C%20not%20document%20sets%20per%20se)%20and%20InfoPath%20forms-based%20input%20(for%20which%20there%20is%20still%20no%20sensible%20replacement%20available%20to%20me).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-368348%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-368348%22%20slang%3D%22en-US%22%3EIt%E2%80%99s%20now%20on%20slashdot%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fm.slashdot.org%2Fsubmission%2F9358382%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fm.slashdot.org%2Fsubmission%2F9358382%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-366836%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-366836%22%20slang%3D%22en-US%22%3E%3CP%3EAlso%20disappointed%20with%20the%20management%20of%20this%20issue.%20I%20do%20have%20access%20to%20the%20Health%20Service%20for%20our%20tenant%20and%20there%20is%20%3CSTRONG%3Enothing%3C%2FSTRONG%3E%20posted%20about%20this%20incident.%20Being%20unaware%20of%20the%20current%20situation%2C%20we%20tried%20to%20publish%20updates%20to%20several%20SP2010%20workflows%2C%20which%20are%20now%20broken.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFeels%20very%20much%20like%20Microsoft%20is%20trying%20to%20hide%20this%20issue%2C%20which%20is%20having%20a%20huge%20impact%20on%20many%20businesses.%20And%20we%20do%20still%20need%20SP2010%20workflows%20since%20both%20Flow%20and%20SP2013%20are%20lacking%20some%20of%20the%20same%20functionality.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-366586%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-366586%22%20slang%3D%22en-US%22%3EWe%20have%20the%20same%20problem%20on%20our%20tenant.%3CBR%20%2F%3EAfter%20trying%20to%20publish%20the%20workflow%2C%20the%20workflows%20are%20now%20not%20working%20as%20expected.%3CBR%20%2F%3EI'm%20getting%20the%20below%20error%3A%3CBR%20%2F%3ERetrying%20last%20request.%20Next%20attempt%20scheduled%20after%203%2F13%2F2019%208%3A54%20AM.%20Details%20of%20last%20request%3A%20HTTP%20BadRequest%20to%20https%3A%2F%2Ftenant%2Fsites%2FSiteCollection%2F_api%2FSP.WorkflowServices.InteropService.Current%2FStartWorkflow%20Correlation%20Id%3A%20a351b5ff-0af8-84e8-a2ad-446ba66c7012%20Instance%20Id%3A%209dd661b4-a031-474e-ade4-c4b9ba58b6c2%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-365118%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-365118%22%20slang%3D%22en-US%22%3E%3CP%3ENothing%20changes.%20Any%20other%20news%20about%20the%20timing%20about%20the%20resolution%20of%20this%20issue%3F%3CBR%20%2F%3EAny%20workaround%3F%3CBR%20%2F%3EI'm%20just%20migrate%20an%20intranet%20from%20on%20premise%20to%20cloud%20and%20tomorrow%20I'll%20start%20the%20training%20to%20the%20staff.%20It's%20not%20a%20good%20starting%20point%20what%20is%20happening.%20I%20hope%20MS%20guys%20understand%20soon%20as%20possible%20that%20for%20us%20who%20work%20with%20Sp%20it's%20difficult%20to%20explain%20to%20the%20rest%20of%20the%20world%20what%20is%20happening.%20Im%20sure%20that%20the%20trouble%20will%20be%20solved.%20But%20it's%20not%20a%20good%20thing%20that%20no%20one%20of%20us%20knows%20why%20that%26nbsp%3Bwas%20happen%20and%20when%20MS%20will%20solve%20the%20problem.%20We%20have%20to%20explain%20it%20to%20other%20people.%20All%20the%20best.%20D.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-364772%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364772%22%20slang%3D%22en-US%22%3E%22as%20expected%22%3CBR%20%2F%3E%3CBR%20%2F%3EYep%2C%20pretty%20much.%20A%20five%20day%2B%20outage%20of%20core%20functionality%20is%20what%20we%20have%20come%20to%20expect.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-364755%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364755%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20everyone%20-%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F299104%22%20target%3D%22_blank%22%3E%40DenisCheong%3C%2FA%3E%26nbsp%3Bis%20right.%26nbsp%3B%20I'm%20just%20a%20Microsoft%20customer%20like%20the%20rest%20of%20you.%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20I%20shared%20was%20the%20message%20that%20I%20saw%20in%20our%20Office%20365%20tenant's%20service%20health%20dashboard.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECurrently%2C%20the%20message%20I%20see%20has%20this%20as%20the%20current%20status%20(%3CEM%3EUpdated%3A%202019-03-11%2019%3A08%20(UTC))%3C%2FEM%3E%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3E%3CSPAN%3ECurrent%20status%3A%20Our%20work%20to%20develop%20a%20mitigation%20solution%20is%20progressing%20as%20expected%20and%20is%20being%20treated%20at%20the%20highest%20priority.%20We'll%20provide%20a%20timeline%20for%20mitigation%20as%20soon%20as%20it%20becomes%20available.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-364747%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364747%22%20slang%3D%22en-US%22%3E%3CP%3ENo%20change%20in%20status%20that%20I%20can%20see.%26nbsp%3B%20Still%20basically%20%22we%20are%20working%20on%20it%22%20and%20that's%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-364735%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364735%22%20slang%3D%22en-US%22%3EDoes%20anybody%20following%20this%20thread%20have%20access%20to%20the%20Microsoft%20dashboard%20with%20the%20resolution%20status%3F%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fportal.office.com%2FAdminPortal%2FHome%23%2Fservicehealth%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fportal.office.com%2FAdminPortal%2FHome%23%2Fservicehealth%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-364728%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364728%22%20slang%3D%22en-US%22%3E%3CP%3EAnd%20not%20chasing%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1273%22%20target%3D%22_blank%22%3E%40Kelly%20Jones%3C%2FA%3E%20-%20meerly%20venting%20frustation%20%3A)%3C%2Fimg%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-364711%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364711%22%20slang%3D%22en-US%22%3E%3CP%3EGoogle%20has%20now%20indexed%20another%20page%20with%20more%20details%20on%20this%20outage%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fanswers.microsoft.com%2Fen-us%2Fmsoffice%2Fforum%2Fall%2Funable-to-unpdate-workflow-in-sharepoint-designer%2Fcacd70f9-2ed6-4db3-a55b-b9284251571e%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fanswers.microsoft.com%2Fen-us%2Fmsoffice%2Fforum%2Fall%2Funable-to-unpdate-workflow-in-sharepoint-designer%2Fcacd70f9-2ed6-4db3-a55b-b9284251571e%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-364707%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364707%22%20slang%3D%22en-US%22%3E%3CP%3ETo%20his%20credit%2C%20I%20don't%20think%20that%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1273%22%20target%3D%22_blank%22%3E%40Kelly%20Jones%3C%2FA%3E%20works%20for%20Microsoft%2C%20but%20he%20does%20have%20access%20to%20Microsoft's%20service%20health%20dashboard%20(which%20I%20don't%20have%20and%20they%20don't%20publish%20online%20that%20I%20know%20of).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20is%20very%20poor%20service%20and%20service%20integration%20that%20there%20can%20be%20a%20global%20outage%20of%20this%2C%20which%20has%20lasted%20so%20long%20(coming%20up%20to%20a%20week%20now)%20with%20neither%20a%20public%20disclosure%20nor%20a%20private%20disclosure%20that%20permeates%20down%20to%20me%20as%20a%20business%20user%20%2F%20site%20collection%20admin%20(which%20is%20a%20service%20management%20integration%20issue%20between%20my%20support%20organisation%20and%20Microsoft%2C%20which%20exists%20in%20most%20if%20not%20all%20of%20their%20large%20corporate%20customers).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20also%20still%20don't%20understand%20why%20there%20is%20still%20a%20core%20functionality%20gap%20between%20SharePoint%202010%20workflows%20and%20their%20replacements%20(2013%20workflows%20and%20Flow)%20which%20also%20means%20we%20can't%20avoid%20relying%20on%20them%20to%20function%20-%20and%20have%20no%20possible%20workaround%20during%20this%20outage.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-364699%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364699%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Kelly%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%20i%20find%20it%20remarkable%20that%20this%20type%20of%20issue%20can%20occur.%20I%20Believe%20not%20only%20our%20business%20but%20many%20other%20is%20also%20getting%20damaged%20by%20this%20kind%20of%20outtage.%20We%C2%B4ve%20got%20business%20critical%20processes%20that%20are%20at%20standstill%2C%20causing%20significant%20financial%2Fbusiness%20damage.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-364696%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364696%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20has%2Fis%20been%20extremely%20poorly%20managed%20by%20Microsoft.%20We%C2%B4ve%20got%20business%20critical%20workflows%20as%20well%20that%20are%20now%20no%20longer%20operational.%20And%2C%20there%20is%20very%20Little%20Comfort%20in%20the%20data%20shared%20by%20Microsoft%20on%20when%20this%20issue%20is%20fixed.%20Makes%20us%20reconsider%20using%20Sharepoint%20onward%2C%20as%20our%20financial%20loss%20for%20this%20outtage%20is%20quite%20considerable.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-364692%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364692%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20actually%20worse%20for%20us%20-%20I%20have%20broken%20a%20business%20critical%20workflow%20by%20attempting%20to%20publish%20an%20updated%20version%20of%20it%20last%20week%20-%20due%20to%20the%20outage%20it%20is%20now%20no%20longer%20associated%20to%20the%20list%2C%20and%20cannot%20be%20run%20(it%20just%20gives%20a%20blank%20page%20with%20a%20%22%5C%22%20at%20the%20top%20of%20it).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-364629%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364629%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20the%20same%20problem%20on%20our%20tenant.%3CBR%20%2F%3EI%20can't%20edit%20any%202010%20workflow%20or%20publish%20new%20ones.%26nbsp%3B%20I%20really%20hope%20that%20MS%20solve%20soon%20this%20problem.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-364591%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364591%22%20slang%3D%22en-US%22%3E%3CP%3E%2B1%20can%20we%20please%20have%20an%20update%20on%20resolving%20this.%26nbsp%3B%20I've%20spent%20half%20a%20day%20isolating%20the%20issue%20to%20%22not%20me%22%20and%20was%20fortunate%20enough%20to%20find%20this%20post%20through%20Google.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThese%20types%20of%20major%20issues%20deserve%20broader%20visibility%20to%20the%20affected%20people.%26nbsp%3B%20It%20first%20occurred%20on%20Friday%20last%20week.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-364584%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364584%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Kelly%3C%2FP%3E%3CP%3EDo%20we%20have%20any%20updates%20to%20this%20issue%3F%20few%20workflows%20in%20our%20production%20system%20are%20impacted.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-364170%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364170%22%20slang%3D%22en-US%22%3E%3CP%3E%3CEM%3EOur%20Service%20Health%20Dashboard%20has%20an%20entry%20for%20this%3A%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22flyout-header%22%3E%3CDIV%20class%3D%22flyout-head-title%20flyout-head_trim%20pc-header%22%3E%3CH1%20id%3D%22toc-hId-1875385090%22%20id%3D%22toc-hId-1899550490%22%20id%3D%22toc-hId-1899550490%22%20id%3D%22toc-hId-1899550490%22%20id%3D%22toc-hId-1899550490%22%20id%3D%22toc-hId-1899550490%22%20id%3D%22toc-hId-1899550490%22%20id%3D%22toc-hId-1899550490%22%20id%3D%22toc-hId-1899550490%22%20id%3D%22toc-hId-1899550490%22%3ESP175429%20-%20Unable%20to%20edit%20existing%20workflows%20or%20create%20new%20workflows%3C%2FH1%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22flyoutContent%22%3E%3CDIV%20class%3D%22shd%20message-detail%22%3E%3CDIV%20class%3D%22message-body%22%3E%3CDIV%20class%3D%22row%22%3E%3CDIV%20class%3D%22col-xs-8%20col-sm-8%20col-md-8%20col-lg-8%20override-padding%22%3E%3CDIV%20class%3D%22details%22%3E%3CDIV%20class%3D%22content%22%3E%3CDIV%20class%3D%22row%22%3E%3CDIV%20class%3D%22field%22%3E%3CDIV%20class%3D%22col-xs-3%20col-sm-3%20col-md-3%20col-lg-3%20override-padding%22%3E%3CSPAN%20class%3D%22bold%22%3EStatus%3A%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%20class%3D%22pre-wrap%22%3EService%20degradation%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22row%22%3E%3CDIV%20class%3D%22field%22%3E%3CDIV%20class%3D%22col-xs-3%20col-sm-3%20col-md-3%20col-lg-3%20override-padding%22%3E%3CSPAN%20class%3D%22bold%22%3EUser%20impact%3A%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%20class%3D%22pre-wrap%22%3EUsers%20are%20unable%20to%20edit%20workflows%20or%20create%20new%20workflows%20in%20SharePoint%202010%20using%20Designer%20and%20other%20protocols.%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22row%22%3E%3CDIV%20class%3D%22field%22%3E%3CDIV%20class%3D%22col-xs-3%20col-sm-3%20col-md-3%20col-lg-3%20override-padding%22%3E%3CSTRONG%3ETitle%3C%2FSTRONG%3E%3A%20Unable%20to%20edit%20existing%20workflows%20or%20create%20new%20workflows%3C%2FDIV%3E%3CDIV%20class%3D%22col-xs-9%20col-sm-9%20col-md-9%20col-lg-9%20override-padding%22%3E%3CSPAN%20class%3D%22pre-wrap%22%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20class%3D%22col-xs-9%20col-sm-9%20col-md-9%20col-lg-9%20override-padding%22%3E%3CSPAN%20class%3D%22pre-wrap%22%3E%3CSTRONG%3EUser%20Impact%3A%3C%2FSTRONG%3E%20Users%20are%20unable%20to%20edit%20workflows%20or%20create%20new%20workflows%20in%20SharePoint%202010%20using%20Designer%20and%20other%20protocols.%26nbsp%3B%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20class%3D%22col-xs-9%20col-sm-9%20col-md-9%20col-lg-9%20override-padding%22%3E%3CSPAN%20class%3D%22pre-wrap%22%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20class%3D%22col-xs-9%20col-sm-9%20col-md-9%20col-lg-9%20override-padding%22%3E%3CSPAN%20class%3D%22pre-wrap%22%3E%3CSTRONG%3EMore%20info%3A%3C%2FSTRONG%3E%20Users%20may%20receive%20the%20error%3A%20%22Unexpected%20error%20on%20server%20associating%20the%20workflow%2C%22%20and%20%22Errors%20were%20found%20when%20compiling%20the%20workflow.%20The%20Workflow%20files%20were%20saved%20but%20cannot%20run.%22%26nbsp%3B%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20class%3D%22col-xs-9%20col-sm-9%20col-md-9%20col-lg-9%20override-padding%22%3E%3CSPAN%20class%3D%22pre-wrap%22%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20class%3D%22col-xs-9%20col-sm-9%20col-md-9%20col-lg-9%20override-padding%22%3E%3CSPAN%20class%3D%22pre-wrap%22%3E%3CSTRONG%3ECurrent%20status%3A%3C%2FSTRONG%3E%20We're%20making%20progress%20on%20our%20development%20of%20a%20viable%20mitigation%3B%20though%2C%20we%20continue%20to%20expect%20that%20it%20may%20take%20an%20extended%20period%20of%20time%20to%20complete.%20We%20do%20anticipate%20that%20we'll%20have%20a%20timeline%20for%20delivery%20within%20the%20next%20few%20days.%26nbsp%3B%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20class%3D%22col-xs-9%20col-sm-9%20col-md-9%20col-lg-9%20override-padding%22%3E%3CSPAN%20class%3D%22pre-wrap%22%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20class%3D%22col-xs-9%20col-sm-9%20col-md-9%20col-lg-9%20override-padding%22%3E%3CSPAN%20class%3D%22pre-wrap%22%3E%3CSTRONG%3EScope%20of%20impact%3C%2FSTRONG%3E%3A%20Impact%20is%20specific%20to%20SharePoint%202010%20workflows.%20Any%20user%20attempting%20to%20edit%20existing%20workflows%20or%20create%20new%20workflows%20may%20be%20affected%20by%20this%20event.%26nbsp%3B%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20class%3D%22col-xs-9%20col-sm-9%20col-md-9%20col-lg-9%20override-padding%22%3E%3CSPAN%20class%3D%22pre-wrap%22%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20class%3D%22col-xs-9%20col-sm-9%20col-md-9%20col-lg-9%20override-padding%22%3E%3CSPAN%20class%3D%22pre-wrap%22%3E%3CSTRONG%3ENext%20update%20%3C%2FSTRONG%3Eby%3A%20Monday%2C%20March%2011%2C%202019%2C%20at%208%3A00%20PM%20UTC%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-754231%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-754231%22%20slang%3D%22en-US%22%3EHi%2C%20I%20have%20the%20same%20problem%20as%20mentioned%20early%20%22Unexpected%20Error%20on%20server%20associating%20the%20workflow%22.%20I%20couldn't%20publish%20workflow%20when%20checked%20the%20condition%20(create%2Fchanged%20automatically).%20Could%20you%20help%20me%20with%20this%20issue%20or%20share%20some%20guidelines.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-758140%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-758140%22%20slang%3D%22en-US%22%3EThis%20original%20thread%20is%20about%20a%20specific%20issue%20that%20was%20caused%20by%20a%20failed%20Microsoft%20change%20that%20affected%20all%20Office%20365%20SharePoint%20instances%2C%20which%20is%20now%20resolved%20(and%20is%20still%20resolved%20for%20us).%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20you%20have%20this%20error%20still%2C%20then%20it%20is%20caused%20by%20some%20other%20issue%20that%20isn't%20related%20to%20this%20thread.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-991635%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-991635%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F298574%22%20target%3D%22_blank%22%3E%40Nanovac_AB%3C%2FA%3EThis%20same%20issue%20has%20occurred%20again%20and%20I%20can%20no%20longer%20publish%20any%20SharePoint%202010%20workflows%20(2%20tried).%26nbsp%3B%20Is%20anybody%20else%20seeing%20this%20again%20%3F%3F%20Didn't%20Microsoft%20learn%20from%20the%20first%20time%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEdit%3A%20If%20you%20are%20going%20to%20check%20then%20do%20it%20on%20a%20non-critical%20worfklow!%26nbsp%3B%20Don't%20break%20a%20critical%20workflow%20like%20I%20did.%26nbsp%3B%20The%20symptoms%20are%20the%20same%20-%20existing%20published%20workflows%20are%20fine%2C%20but%20trying%20to%20publish%20a%20new%20one%20will%20fail%20and%20break%20the%20existing%20one.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-991877%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-991877%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F299104%22%20target%3D%22_blank%22%3E%40DenisCheong%3C%2FA%3E%26nbsp%3B%20-%20We%20have%20a%20message%20in%20our%20Service%20Health%20Dashboard%3A%3C%2FP%3E%3CDIV%20class%3D%22flyoutHeaderStyle-214%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22flyoutHeaderStyle-214%22%3E%3CDIV%20class%3D%22flyoutHeaderStyle-214%22%3E%3CSTRONG%3EWorkflows%202010%20issue%3C%2FSTRONG%3E%3C%2FDIV%3E%3CDIV%20class%3D%22flyoutTextStyle-219%22%3E%3CDIV%20class%3D%22subHeaderText-857%22%3ESP194864%2C%20SharePoint%20Online%2C%3C%2FDIV%3E%3CDIV%20class%3D%22subHeaderText-857%22%3ELast%20updated%3A%20November%206%2C%202019%202%3A44%20PM%3C%2FDIV%3E%3CDIV%20class%3D%22subHeaderText-857%22%3EStart%20time%3A%20November%205%2C%202019%2010%3A10%20AM%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%3E%3CDIV%20class%3D%22textLabel-858%22%3EStatus%3A%26nbsp%3B%3CSPAN%3EService%20degradation%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%3E%3CDIV%20class%3D%22textLabel-858%22%3EUser%20impact%3A%26nbsp%3BUsers%20may%20be%20unable%20to%20create%20new%20or%20edit%20existing%20workflows%20under%20Workflows%202010.%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-992169%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-992169%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F299104%22%20target%3D%22_blank%22%3E%40DenisCheong%3C%2FA%3E%26nbsp%3BIm%20also%20having%20the%20same%20issue.%26nbsp%3B%20Is%20there%20a%20fix%20for%20this%20yet%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-993693%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-993693%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1273%22%20target%3D%22_blank%22%3E%40Kelly%20Jones%3C%2FA%3EGreat%20...%20just%20great%20...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-996536%22%20slang%3D%22es-ES%22%3ERe%3A%20Sharepoint%202010%20Workflow%20can%20no%20longer%20be%20published%20on%20Sharepoint%202013%20for%20our%20Online%20site%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-996536%22%20slang%3D%22es-ES%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F299104%22%20target%3D%22_blank%22%3E%40DenisCheong%3C%2FA%3E%20%2C%20we%20have%20the%20same%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethe%20time%20it%20takes%20to%20solve%20this%20problem%20seems%20fatal%20to%20me%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThe%20last%20update%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ETitle%3A%20Workflows%202010%20issue%20User%20Impact%3A%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EUsers%20may%20be%20unable%20to%20create%20new%20or%20edit%20existing%20workflows%20under%20Workflows%202010.%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EMore%20info%3A%20Users%20may%20receive%20the%20error(s)%3A%20%22Unexpected%20error%20on%20server%20associating%20the%20workflow%2C%22%20and%20%22Errors%20were%20found%20when%20compiling%20the%20workflow.%20The%20Workflow%20files%20were%20saved%20but%20cannot%20run.%22%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EUsers%20will%20experience%20relief%20as%20the%20activity%20progresses%20within%20the%20environment.%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ECurrent%20status%3A%20We've%20validated%20that%20the%20deployment%20is%20now%20progressing%20as%20expected%20and%20we're%20monitoring%20its%20status%20to%20ensure%20it%20completes%20successfully.%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EScope%20of%20impact%3A%20This%20issue%20may%20potentially%20affect%20any%20of%20your%20users%20attempting%20to%20create%20new%20or%20edit%20existing%20workflows%20within%20SharePoint%20Designer%202013%2C%20under%20Workflows%202010.%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EStart%20time%3A%20Tuesday%2C%20November%205%2C%202019%2C%209%3A23%20AM%20(2%3A23%20PM%20UTC)%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ERoot%20cause%3A%20Our%20analysis%20identified%20that%20the%20infrastructure%20responsible%20for%20Workflows%202010%20functionality%20contained%20a%20misconfiguration.%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ENext%20update%20by%3A%20Monday%2C%20November%2011%2C%202019%2C%203%3A30%20PM%20(8%3A30%20PM%20UTC)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Dear all, 

 

 we run a SharePoint Online site, where we have a number of workflows (2010) running mainly to generate documents etc in our automated workflows. All has been working fine, till today, when we had some modifications we wanted to execute on some of the 2010 workflows. We are using Sharepoint designer 2013. When saving the workflow, there are no issues, but when we try to publish we get an error (see attached) [Unexpected error on server associating the workflow]

 

Skärmklipp 2019-03-11 10.37.18.png

Right now, we´re at a standstill, and I can not find any real relevant information online on this. Some "older" stuff on temporary files etc have been reviewed, but without success. 

 

Pretty desperate now to get some help - Everything is much appreciated. 

45 Replies
Highlighted
Hi, I have the same problem as mentioned early "Unexpected Error on server associating the workflow". I couldn't publish workflow when checked the condition (create/changed automatically). Could you help me with this issue or share some guidelines.
Highlighted
This original thread is about a specific issue that was caused by a failed Microsoft change that affected all Office 365 SharePoint instances, which is now resolved (and is still resolved for us).

If you have this error still, then it is caused by some other issue that isn't related to this thread.
Highlighted

@Nanovac_ABThis same issue has occurred again and I can no longer publish any SharePoint 2010 workflows (2 tried).  Is anybody else seeing this again ?? Didn't Microsoft learn from the first time??

 

Edit: If you are going to check then do it on a non-critical worfklow!  Don't break a critical workflow like I did.  The symptoms are the same - existing published workflows are fine, but trying to publish a new one will fail and break the existing one.

Highlighted

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

 
Workflows 2010 issue
SP194864, SharePoint Online,
Last updated: November 6, 2019 2:44 PM
Start time: November 5, 2019 10:10 AM
Status: Service degradation
User impact: Users may be unable to create new or edit existing workflows under Workflows 2010.
Highlighted
Highlighted

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)