Problem with new connection manager

Enrico Knapp‌ that might be stupid, but are you sure you chose the right level of permissions, when configuring access? See: https://help.nintex.com/en-US/O365/Default.htm#o365/O365WorkFlow/Connections.htm%3FTocPath%3DUse%2520advanced%2520techni… 

Yeah, that was stupid. You checked it. You chose the right level. 

One question - are you using different account to provide permissions than the one, you are logged in when designing your workflow?

Regards,

Tomasz

Hi ,

thanks for replying. I'm using the same account for creating the connection and creating the workflow. Only the credentials in the connection are different.

I reached out to Nintex support and still hope for help.

Best regards

Enrico

Thanks for replying Tomasz,

I'll have a look at it and try it out.

Best regards

Enrico

Hello Enrico,

did you find an answer for this. I'm also having the issue.

kind regards,

Jim

Hi Jim,

the problem in my case was that I didn't give the account named in the permission also the owner permissions on the site. After I made the account also a site owner it worked for me.

Best regards

Enrico

Hi Jim,

Are you able to resolve your issue ?

I have worked on the connection manager and followed the below way to accomplish that:

I have login the SharePoint site and trying to develop the Nintex workflow with my own credentials (for example: Giridhar@xyz.com) but in my case the credentials that I am trying to give in connection manager is different ( admin@xyz.com). I run the workflow it works fine, but make sure the credentials (in my case admin@xyz.com) have necessary permissions over the site to run the workflow.

Let me know if you still have any issues.

Thanks,

Giridhar  

Hello, 

that did it for me as well. I assumed that site collection admin would have been enough, but apparently the site on which the flow is running, also needs direct permissions (in person, or via a group).

Tnx so very much for your reply

I am having the same issue.

Can you explain what the proper way of working must be ?

It's very confusing and don't understand why Nintex makes this a horrible m....sss after about working with the product and permission action since 2006 :-)

I am also having the same issue.  Sometimes the error goes away if I just restart the workflow after it suspends.  But not always.  Seems like the Connections feature was rushed out the door and it's still buggy.  So frustrating to deal with this nonsense.   I have a client that needs me to finish this for a high visibility project.  And the product just doesn't work.  Getting harder to recommend Nintex with each passing day.  

Same here.