We are having this issue in SP Workflow 2013 that even we create a simple workflow like sending email or just changing status name it always goes to Suspended stage.

Below is the error we always experience:

enter image description here

RequestorId: 1236f263-86b3-1728-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ApplicationException: HTTP 401 {"error_description":"The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs."} {"x-ms-diagnostics":["3001000;reason=\"There has been an error authenticating the request.\";category=\"invalid_client\""],"SPRequestGuid":["1236f263-86b3-1728-b863-e8c83aefd80d"],"request-id":["1236f263-86b3-1728-b863-e8c83aefd80d"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"SPRequestDuration":["42"],"SPIisLatency":["1"],"Server":["Microsoft-IIS/8.5"],"WWW-Authenticate":["Bearer realm=\"9445b918-6209-4438-900e-2e406a825b5f\",client_id=\"00000003-0000-0ff1-ce00-000000000000\",trusted_issuers=\"00000005-0000-0000-c000-000000000000@*,00000003-0000-0ff1-ce00-000000000000@9445b918-6209-4438-900e-2e406a825b5f\"","NTLM"],"X-Powered-By":["ASP.NET"],"MicrosoftSharePointTeamServices":[""],"X-MS-InvokeApp":["1; RequireReadOnly"],"Date":["Wed, 22 Jul 2015 02:30:12 GMT"]} at Microsoft.Activities.Hosting.Runtime.Subroutine`1.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)

We already configured SMTP Mail, User Profile Service in our server but we still cant still make SP Worflow 2013 work.

Other thing that I noticed, the modified by in 2013 is using domain/username but in 2010 its using UserName [DomainGroup].

  • Is this a Designer or Visual Studio workflow? Do all actions fail (write to history, update list item, query web service) or just specific ones (email)?
    – Graham
    Commented Jul 22, 2015 at 3:05
  • We only use SharePoint Designer. All the actions failed, the workflow started but it goes to suspended.
    – BizApps
    Commented Jul 22, 2015 at 3:10
  • Is it sharepoint online or on prem?
    – Waqas Sarwar MVP
    Commented Jul 22, 2015 at 3:36
  • 1
    I had once a problem with my memory (over 90% were used) and also don't try the workflow as a systemaccount.
    – Patrick
    Commented Jul 22, 2015 at 6:31

4 Answers 4


Okay, after weeks of struggling here I found the solution.

I just need to activate Workflow can use app permissions in Site Settings and create elevated permission.

I followed this link: Create a workflow with elevated permissions by using the SharePoint 2013 Workflow platform Hope this helps!


While creating the 2013 workflow go the workflow settings and uncheck the "Automatically update the workflow status to the current status" checkbox.

In the workflow, just write a log to history list and try to publish. Check if the workflow is working.


Inadequate App Step permissions is usually the source of this error. I solved it by enabling an App Step Feature, and granting permissions to the App Step. For detailed steps, please see: http://www.reality-tech.com/workflow-error-in-sp2013-related-to-app-step/


The HTTP 401 error (Unauthorized) resulting in workflow Suspended internal status also occurs when the initiator of the workflow no longer has access to the list item (or other items to be updated by the workflow).

For example, consider a user who creates a list item, initiating a workflow that creates a task for someone else. If the initiator leaves the enterprise and is removed from active directory, when the task is completed, this same HTTP 401 result happens if the workflow then tries to update the workflow status for that list item.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.