Reviving SharePoint Designer Workflow From Suspended Status, Programmatically

Introduction

This article helps to get you started by explaining some key design considerations and providing a basic procedure. In this article, we will see about SharePoint Designer Workflow, when it is in suspended status, and how we can retrieve it programmatically. In the last section, you can find the links to complete Workflow examples.

Why we are using SharePoint designer Workflow?

We can design Workflows that add an Application logic to your site or an Application without writing a custom code.

Types of workflows

All SharePoint Workflows are associated with a SharePoint list/site. We have three different types of Workflows which can start and are given below.

List Workflow
Reusable Workflow
Site Workflow

Before doing a deep dive on Workflows, first we will see about how to work on SharePoint Designer Workflows.

Create a SharePoint 2013 Designer Workflow steps

Click Workflows section in the top navigation.
We have three different Workflows. Select anyone -> List Workflowdrop-down in the New section of the ribbon.
Choose the list with which we want to attach it.

Enter the basic details. Create List Workflow dialog box and then make sure that the platform type is set to SharePoint 2013 Workflow.

The procedure given above is used to create a List Workflow. A reusable Workflow or site Workflow can be created, using the same procedure with the modification given below.

Suspend/terminate Workflows automatically

Sometimes Workflows cannot start and it has been terminated/suspended automatically. We can see it in a Workflow settings page, see the status for the initiated Workflow, as suspended or canceled.

Example

This is the sample issue listed but many errors can occur, like the status given below.

The Workflow Information page displays an error message that resembles what is shown below.

See the error message given below.

RequestorId: ac01a77b-619a-dbd2-0000-000000000000.

Details

An unhandled exception occurred during the execution of the Workflow instance.

Exception details

System.ApplicationException: HTTP 401 {
"Transfer-Encoding": ["chunked"],
"X-SharePointHealthScore": ["0"],
"SPClientServiceRequestDuration": ["864"],
"SPRequestGuid": ["ac01a77b-619a-dbd2-aa49-a4d2580be234"],
"request-id": ["ac01a77b-619a-dbd2-aa49-a4d2580be234"],
"X-FRAME-OPTIONS": ["SAMEORIGIN"],
"MicrosoftSharePointTeamServices": ["15.0.0.4631"],
"X-Content-Type-Options": ["nosniff"],
"X-MS-InvokeApp": ["1; RequireReadOnly"],
"Cache-Control": ["max-age=0, private"],
"Date": ["Mon, 12 Jan 2015 20:03:16 GMT"],
"Server": ["Microsoft-IIS\/8.5"],
"WWW-Authenticate": ["NTLM"],
"X-AspNet-Version": ["4.0.30319"],
"X-Powered-By": ["ASP.NET"]
}
at Microsoft.Activities.Hosting.Runtime.Subroutine
SubroutineChild.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at
System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)

The code given below will execute in the site level and retrieve all the suspended Workflows programmatically.

Open your Visual Studio.
Select the console Application.
Copy and paste the code given below.

Source code

using Microsoft.SharePoint.Client;
using Microsoft.SharePoint.Client.WorkflowServices;
using System;
using System.Linq;
using System.Security;
namespace GowthamWFTutorial {
class Program {
static void Main(string[] args) {
string list = "TutorialWFList";
string workflowName = "TestWorkflow";
var workflowStatus = WorkflowStatus.Suspended;
var Context = SP.ClientContext.get_current();
Web web = Context.Web;
Guid listGUID = GetListGUID(Context, list);
var wfServicesManager = new WorkflowServicesManager(Context, web);
var wfSubscriptionService = wfServicesManager.GetWorkflowSubscriptionService();
var wfSubscriptions = wfSubscriptionService.EnumerateSubscriptionsByList(listGUID);
clientContext.Load(wfSubscriptions, wfSubs => wfSubs.Where(wfSub => wfSub.Name == workflowName));
clientContext.ExecuteQuery();
var wfSubscription = wfSubscriptions.First();
var wfInstanceService = wfServicesManager.GetWorkflowInstanceService();
var wfInstanceCollection = wfInstanceService.Enumerate(wfSubscription);
clientContext.Load(wfInstanceCollection, wfInstances => wfInstances.Where(wfI => wfI.Status == workflowStatus));
clientContext.ExecuteQuery();
foreach(var wfInstance in wfInstanceCollection) {
Console.WriteLine(wfInstance.Properties["Microsoft.SharePoint.ActivationProperties.CurrentItemUrl"]);
}
Console.ReadKey();
}
private static Guid GetListGUID(ClientContext context, string listTitle) {
var list = context.Web.Lists.GetByTitle(listTitle);
context.Load(list, l => l.Id);
context.ExecuteQuery();
return list.Id;
}
}
}

You cannot change which list a Workflow is attached to after you save the Workflow. Thus, we have to create a new Workflow and attach it to the list which you want.

Conclusion

This article explains about the basic creation of Workflows and how to get the suspended/terminated Workflows, using Client Object model. By now, you must have understood the key concepts and design considerations, so you might want to design a Workflow, which has a specific application.