SharePoint Designer WorkFlow Suspended: HTTP 401 Error

The Matrix Has YouSharePoint error messages typically need a Rosetta stone, a gallon of coffee, and the patience of Mother Theresa to troubleshoot. This one is no different.

SharePoint Designer WorkFlow Suspended
SharePoint Designer WorkFlow Suspended


First thing you’ll notice is that the workflow is suspending and never going anywhere after that. When you click on the little “i” icon, you’ll get the error message in a dialogue window. It’ll look something like this…

RequestorId: 889c3c8c-e88a-e968-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":["47"],"SPRequestGuid":["889c3c8c-e88a-e968-b09f-f72cf5e9f776"],"request-id":["889c3c8c-e88a-e968-b09f-f72cf5e9f776"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"Cache-Control":["max-age=0, private"],"Server":["Microsoft-IIS\/8.0"],"WWW-Authenticate":["Negotiate","NTLM"],"X-AspNet-Version":["4.0.30319"],"X-Powered-By":["ASP.NET"],"MicrosoftSharePointTeamServices":[""],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1; RequireReadOnly"],"Date":["Tue, 14 Mar 2017 18:33:03 GMT"]} 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)

It might as well be written in green-glowing characters dropping from the top of the screen.

The trick is to catch it when the workflow’s “internal status” is still “Started” and not “Suspended.” By the time it’s suspended, the useful error message is gone.

If you catch it in “Started” and click that little icon, you’ll get an error message like this…

Activity in progress.Retrying last request.
Next attempt scheduled in less than one minute.
Details of last request: HTTP Unauthorized to https://{yourserver}/_vti_bin/client.svc/web/lists(guid'some-list-guid')/Items
Correlation Id: 889c3c8c-e88a-e968-b51c-************
Instance Id: 9ae31cf2-230a-4d64-949c-b0d22a2eae72

Now, we’re getting somewhere. This not only tells us the user is “unauthorized” but it tells us what they are unauthorized to.


You might recognize it as a REST API call! Strip “/Items” off the tail end of the url and you’ll get the list in question- in this case, the WorkFlow History list. If the user can’t write to it, the workflow can’t do much.

This might be the same for you. But, regardless of the list in question, now you can go and modify permissions on it so users can execute workflows.

Just elevate their permissions to “Contribute” at a minimum, and you’re good to go.

Something else I noticed, for those of you who enjoy digging though ULS logs- The first three segments of the “Started” message’s “Correlation Id” match the first three of the “Suspended” message’s “RequestorId.”

RequestorId: 889c3c8c-e88a-e968-0000-000000000000
Correlation Id: 889c3c8c-e88a-e968-b51c-************

So, if all you have is the RequestorId, you can dive into the logs and narrow down your search.

I hope this helps!


The Matrix Has You

What the heck is SharePoint and how do I use it?!

I get asked this question more than almost any other.

Trying to pull back on the geek-speak: Microsoft SharePoint is a suite of web-based tools and services that dovetail nicely with MS Office applications like Outlook, Excel, Word, etc. It’s used, primarily, as a content/document management solution but is also used for collaboration, communication, even externally facing web sites.

Like many products from Microsoft, SharePoint is available in a variety of tiers (like Foundation, Standard, Enterprise, etc.) each of which come with a variety of capabilities and features.

How your organization uses SharePoint is entirely up to them.

Like making pizza- there is no single “right way.” But there are plenty of wrong ways. (Pineapple? Really? Please.)

Let’s start with the core unit of SharePoint functionality- The “List”

A “list” is just that- a list. It’s a way to store and track items you have some level of interest in. Like a grocery list. You might have “Eggs, milk, butter, bread, orange juice.” So, at first, in SharePoint, your list might look like this…

A basic SharePoint list.
A basic SharePoint list.

That’s fine. You intuitively know certain things about the items in this list that you are tracking in your head. But, if you sent someone else to the store to pick up these items you might not get exactly what you want. Eggs- What kind? Brown, white, speckled? One dozen? Two dozen? Milk- Whole? 2%? One gallon? A Half-gallon? And, as your list grows, you are also categorizing items in your head. i.e. Meat, vegetables, dairy.

See where I’m going with this? All this extra information about the items on your list is what SharePoint calls “metadata” or “data about data.” So let’s add this metadata to our basic grocery list. (Exactly how to add metadata is a topic for another post.)

A SharePoint list with metadata
A SharePoint list with metadata

Now, you can print this out and send someone to the store with it and you’ve got a reasonably good chance of getting what you actually want.

But this list is kind of erratic. If they went in order of the display, they’d spend all afternoon popping back and forth across the store. You could have taken the time to enter the items in proper order- but what if you think of something later that you need to add and its group of items is at the top? You could also rely on the shopper to organize the list in their head, but that seems kind of inconsiderate.

SharePoint has given you a way of storing information- The List. Now you just need a way of displaying that information in a way that’s more useful to a particular person. And SharePoint gives you that too. It’s called a “view.” Views are just ways of organizing and displaying data.

For our grocery example, we’d like to organize the display of items in our list regardless of how they were entered. There are a few ways to do this- you can sort on columns or create views.

To sort on the columns- just pick one of the headings like Title, Style, Quantity, or Category and click on it. For example, if I click on “Style” my list now displays like this…

Sorting a SharePoint list on a column
Sorting a SharePoint list on a column

Now the list is sorted, alphabetically, by the values in the Style column. If I click “Category” it will sort on that column…

Sorting a SharePoint list on another column
Sorting a SharePoint list on another column

See? Now that view is a little easier to understand for your shopper.

Power TIP:  You can email a link to a particular display by copying the url in the address bar. Then paste it into an email, chat window, or document. Then they can print it if they wish.

You can even filter on certain columns. If I hover over the word “Category” and click that little black triangle, I get a display of filtering options…

Filtering a SharePoint list on a column
Filtering a SharePoint list on a column

If I pick one, or more, my display now only shows the items in those categories. To make the filter go away, just click that little funnel icon next to “Category” and then “Clear filters from Category.”

Clearing a filter on a SharePoint list on a column
Clearing a filter on a SharePoint list on a column

Note: Not all field types are sort-able or filterable. My “Notes” field, being a multi-line text field is one such field.

The trouble with sorting on columns is that it’s not permanent. Once you navigate away from this page, that sorting and filtering goes away. That’s where SharePoint Views come in handy. They are a more permanent way of creating sorted and filtered displays.

A view where items are grouped according to Category would be nice, so let’s do that. (Exactly how to views is also a topic for another post.)

A view on a SharePoint list
A view on a SharePoint list

Much clearer. Now, not only do I have a more organized display of my list items, but I’ve got a count of items in each category.

Let’s say, hypothetically, I’ve got two shoppers on the case and each one is assigned to get items in particular categories. I could create views for them. Shopper “A” is getting Meat & Deli items and Shopper “B” is getting Produce & Dairy. And they will determine who will get the Misc items.

So, three views: Meet & Deli…

A filtered view on a SharePoint list
A filtered view on a SharePoint list

Produce & Dairy…

Another filtered view on a SharePoint list
Another filtered view on a SharePoint list

…and Misc.

Another filtered view on a SharePoint list
Another filtered view on a SharePoint list

Power TIP: You can email a link to a particular view, the same way you could with a link to a display- by copying the url in the address bar. Then paste it into an email, chat window, or document.

You can navigate between views by clicking the view names below the “new item” link or by clicking the ellipses to the right of the view names and selecting the view you want. (You can also create and modify views this way, but again, a topic for another post.)

Navigating SharePoint views
Navigating SharePoint views

This grocery list example may seem overly simplistic, but I hope it has begun to clear some of the fog around what SharePoint’s core functionality is, what it does, and how you can use it.

For example- Instead of “groceries” think “employees.” Instead of “categories” think “departments,” “positions,” “titles,” and “regions.” You’ll quickly start to see how this can be used at work, and why so many organizations do.

I hope this has helped!


[If pineapple pizza is your thing… well, sorry. But I found this kinda funny.]

My Purpose

Note: Not Intended For SharePoint “Developers”
When I hear the word “Developer” I immediately think programmer, coder, server-side deployable solutions, etc. That’s not what I do and it’s not what I’m going to help you do.

The intended purpose of this blog is to provide useful guides and information to help take you from SharePoint “noob” too SharePoint “Super User,” 5 minutes at a time.

Granted, some of the things I’m going to do here will require knowledge of HTML, JavaScript, jQuery, XML, etc. But I did say “Super User” didn’t I? Don’t worry though. I promise to make it as painless as possible 😉

Most of the tips here will not involve anything outside of “Site Owner” permissions. (Don’t know what that is? Perfect! You’re exactly who I’ve created this blog for!