Search by tag «workflow»

Entries found: 1

BPOS to Office 365 Transition Issues: Workflows

One of our clients was recently transitioned from Microsoft's BPOS (Business Productivity Online Suite) to Office 365 as part of the upgrade cycle for Microsoft's Online Services. We encountered a few issues which we resolved, occasionally with (excellent, as always) support by Microsoft's support team. We're going to take the time to highlight a few of the issues that we encountered, in the hope that this will help other BPOS administrators in the future. You can see all of these issues in Support Stories. We'll start with an issue related to workflows, which was easily solved.

TaskLight - Office 365 Workflow Issues after transition to BPOS


We encountered two issues with workflows post-transition to Office 365. The first was that none of the workflows would start at all, the error given in the workflow status being "[Workflow name] failed on Start". This happened for all of the workflows that we had created on the SharePoint site collections that transitioned. The (admittedly very simple) solution for this was to open up SharePoint Designer 2010 (remember, once you've transition to Office 365 you need to use the 2010 version of the programme, not 2007), then open the workflow and press the 'Publish' button on the taskbar - simple!

The second issue was that any issues in-progress during the transition failed when they tried to continue. For this client, this meant that there were a number of workflows which, before transition, had paused for a short amount of time. After transition, these workflows did not restart and the workflows failed. There was no way to directly fix this issue, the only thing to do was to start the workflows again.

Here's hoping this helps to indicate any potential issues that you might have with transitioning from BPOS to Office 365. We'll have more coming over the next few weeks under the category Support Stories, come back then, sign up to the RSS feed or join our newsletter.