Forum Discussion
Nanovac_AB
Mar 11, 2019Copper Contributor
Sharepoint 2010 Workflow can no longer be published on Sharepoint 2013 for our Online site
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,...
Bhaski
Mar 13, 2019Copper Contributor
We have the same problem on our tenant.
After trying to publish the workflow, the workflows are now not working as expected.
I'm getting the below error:
Retrying last request. Next attempt scheduled after 3/13/2019 8:54 AM. Details of last request: HTTP BadRequest to https://tenant/sites/SiteCollection/_api/SP.WorkflowServices.InteropService.Current/StartWorkflow Correlation Id: a351b5ff-0af8-84e8-a2ad-446ba66c7012 Instance Id: 9dd661b4-a031-474e-ade4-c4b9ba58b6c2
After trying to publish the workflow, the workflows are now not working as expected.
I'm getting the below error:
Retrying last request. Next attempt scheduled after 3/13/2019 8:54 AM. Details of last request: HTTP BadRequest to https://tenant/sites/SiteCollection/_api/SP.WorkflowServices.InteropService.Current/StartWorkflow Correlation Id: a351b5ff-0af8-84e8-a2ad-446ba66c7012 Instance Id: 9dd661b4-a031-474e-ade4-c4b9ba58b6c2
- amahlochMar 13, 2019Copper Contributor
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.
- DenisCheongMar 13, 2019Brass ContributorIt’s now on slashdot:
https://m.slashdot.org/submission/9358382