All of my SharePoint 2013 workflows fail some sort of “Authentication Exception” in SharePoint Designer

Anonymous
2017-04-23T12:46:52+00:00

Hello

All of my SharePoint 2013 workflows fail some sort of “Authentication Exception”

  • If I try to publish a workflow if fails on the following error.

Microsoft.Workflow.Client.AuthenticationException: Authentication Failed. Valid credentials must be provided for one of the following protocols: Bearer. HTTP headers received from the server - ActivityId: c4abb0c9-6779-410c-a8b8-4a94330e1a9c. NodeId: WFFE_IN_13. Scope: /spo. WWW-Authenticate: Bearer realm="a2b6f772-f7c4-484d-b9a6-1d76301f139f", client_id="00000005-0000-0000-c000-000000000000", trusted_issuers="00000001-0000-0000-c000-000000000000@a2b6f772-f7c4-484d-b9a6-1d76301f139f", scope="/sp

  • If I try to delete the 2013 workflow from SharePoint web interface I get the following error (The same error)

Microsoft.Workflow.Client.AuthenticationException: Authentication Failed. Valid credentials must be provided for one of the following protocols: Bearer. HTTP headers received from the server - ActivityId: 4690d90d-0bc2-40eb-b99a-99bbf3918a7a. NodeId: WFFE_IN_1. Scope: /spo. WWW-Authenticate: Bearer realm="a2b6f772-f7c4-484d-b9a6-1d76301f139f", client_id="00000005-0000-0000-c000-000000000000", trusted_issuers="00000001-0000-0000-c000-000000000000@a2b6f772-f7c4-484d-b9a6-1d76301f139f", scope="/spo

  • If I try to delete a workflow it remains as is (It does not delete)
  • I logged out and signed as a admin (Same issue)
  • I logged into a other user profile on my pc and ran SPD (same issue)
  • I cannot do anything with any 2013 workflow even existing ones that have not been changed
  • SharePoint 2010 workflow work fine.

Look like something on the 365 server side. This just started today.

Can you help?

Thank you,

Grant

Microsoft 365 and Office | SharePoint | For business | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes
Answer accepted by question author
  1. Anonymous
    2017-04-24T11:07:56+00:00

    Hi All,

    Service Health Dashboard has indicated that issue SP99525 has been resolved as of: Monday, April 24, 2017, at 8:49 PM UTC. If you are still experiencing an issue, please let us know as this may indicate either a scoping issue or an independent problem.

    Thanks,

    Fraser

    12 people found this answer helpful.
    0 comments No comments

8 additional answers

Sort by: Most helpful
  1. Anonymous
    2017-04-23T17:44:48+00:00

    Just started getting the exact same thing last night.  I am provisioning sites using REST API.   This worked all day yesterday - no code change today, and yet I am getting this same error.         

    I am also seeing this error now on the Site Workflows page:

    "Some workflows may not be shown. We were unable to reach the workflow service. "

    Opened a ticket with Microsoft   2:51PM  EST

    0 comments No comments
  2. Anonymous
    2017-04-23T19:29:04+00:00

    Im haveing the same exact issue to and it all started last night. I even created a new site and configure the workflow from scratch and I'm stilling receiving that error when I try to

    publish. 

    Microsoft.Workflow.Client.AuthenticationException: Authentication Failed. Valid credentials must be provided for one of the following protocols: Bearer. HTTP headers received from the server - ActivityId: 0f4c77bd-2bb2-4442-b570-c731a11198d2. NodeId: WFFE_IN_4. Scope: /spo. WWW-Authenticate: Bearer realm="a2b6f772-f7c4-484d-b9a6-1d76301f139f", client_id="00000005-0000-0000-c000-000000000000", trusted_issuers="00000001-0000-0000-c000-000000000000@a2b6f772-f7c4-484d-b9a6-1d76301f139f", scope="/spo

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2017-04-23T20:25:21+00:00

    I am on the phone with Microsoft now.  They are having issues from many users across the globe.  It is an issue with 2010 workflows.

    0 comments No comments
  4. Anonymous
    2017-04-23T20:37:11+00:00

    The issue is NOT only related to 2010 workflows. I experience the same publish error with 2013 workflows.

    2 people found this answer helpful.
    0 comments No comments