cancel
Showing results for 
Search instead for 
Did you mean: 
Workflow Hero

Workflow failed due to access denied when querying a list

Jump to solution

One of the initial steps of my workflow is to query a list for some names and set them as variables I use later in the flow.  This is so that if those individuals change positions or leave the company, the content in the workflow can be adjusted appropriately without someone having to make changes to the workflow.

Recently one of my workflows failed and the error details said : 

Failed to query list data. Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

This is not a permissions issue because I was able to start the workflow manually later.  I'm currently under the assumption that this was a momentary hiccup in Sharepoint where the list was unavailable. 

Anyone else run into this?

Labels: (2)
Reply
14 Replies
Workflow Hero

Re: Workflow failed due to access denied when querying a list

Jump to solution

So, is it currently working?

0 Kudos
Reply
Workflow Hero

Re: Workflow failed due to access denied when querying a list

Jump to solution

It works almost all of the time, but I did get this error again recently, so it's happened a couple times now this month, out of about 20-30 workflow runs in the same period, so call it 10% failure rate?  Not great.

0 Kudos
Reply
Workflow Hero

Re: Workflow failed due to access denied when querying a list

Jump to solution

Hello Chris Almaguer‌ - 

When  you say:

This is not a permissions issue because I was able to start the workflow manually later.

Does this mean that you are always starting the workflow or are there other users that are starting it as well?

I have seen issues where users do not have the proper permissions on a site/list that is being queried within the workflow, but have the ability to create new items and kickoff workflows.

You can also try to put the Query list action within an Action set and set the actions within to Run as workflow owner.

Reply
Workflow Hero

Re: Workflow failed due to access denied when querying a list

Jump to solution

This is a good suggestion, but no, it's always either myself or another site owner that's starting the workflow.  The only thing I can think of is that the query that is erroring out is querying multiple values and writing them to multiple variables.  I broke out the query so it's only querying one variable at a time.

This way, I can see WHICH query is causing the error - also if it continues to happen I can add pause actions in between queries to see if that will help.

0 Kudos
Reply
Workflow Hero

Re: Workflow failed due to access denied when querying a list

Jump to solution

I actually went to set this setting anyway, and I don't have this option!  (Nintex 2013).

0 Kudos
Reply
Workflow Hero

Re: Workflow failed due to access denied when querying a list

Jump to solution

did you try this on a branch of a state machine or other branching action?  this option is only available inside an action set when outside of branching logic - can you confirm?

Reply
Workflow Hero

Re: Workflow failed due to access denied when querying a list

Jump to solution

Actually Jesse, I did find out that I was mistaken, some of the folks getting errors are NOT site owners!  I did enable this setting (my action set was nested, I had to go to the parent), and enabled it.  Thanks!

Reply
Workflow Hero

Re: Workflow failed due to access denied when querying a list

Jump to solution

I didn't think I had it because there was no branching, but the action set was nested in another action set (I had to enable this setting on the parent).

Reply
Workflow Hero

Re: Workflow failed due to access denied when querying a list

Jump to solution

I also face the same issue and I am not able to pin point the problem to why it is causing the query being access denied.

In practical it works great as it been working a lot of times until this issue occurred.

I went ahead and added an Action Set and placed the query within the set and ticked the option "run wf as the owner..."

The workflow now works fine but this does not mean the action set fixed the issue lol

0 Kudos
Reply