ERROR when removing the shared SharePoint library in run-only permissions

(0) Share

Report

Posted on by RobMolenaar

112

Hi all,

I have a flow running that's connected to a SharePoint library. The trigger in the flow is "For a selected file."
When I try to disconnect the SharePoint library in the run-only permissions, I get this error: HTTP request failed with unhandled exception of type 'NullReferenceException' and message: 'Object reference not set to an instance of an object.'

I've already tried setting all connections to "Provided by run-only users," but I still get the same error.

Categories:

Process Advisor

I have the same question (0)

All responses (8)

Answers (0)

MS.Ragavendar 4,910 Super User 2025 Season 2 on at

Like (0)

Report
ERROR when removing the shared SharePoint library in run-only permissions

@RobMolenaar,

Open the flow → Details → Run-only users, For each connector (SharePoint, etc.), explicitly set the connection

Use this connection (if you want a service account).

Or Provided by run-only user (if you want user context).

Save changes and save the flow, if you are in the solution based publish solution as well.

✅ Please click Accept as solution if my post helped you solve your issue and help others who will face the similar issue in future.

❤️ Please consider giving it a Like, If the approach was useful in other ways.

🏷️ Please tag me @MS.Ragavendar if you still have any queries related to the solution or issue persists.

Was this reply helpful? Yes No
RobMolenaar 112 on at

Like (0)

Report

ERROR when removing the shared SharePoint library in run-only permissions

Thanks for your reply, but unfortunately that doesn't help.

I've set all connections to run-only user and then tried using the service account connection with all connections. In both cases, I still get the same error message.

Was this reply helpful? Yes No
S-Venkadesh 861 Moderator on at

Like (0)

Report

ERROR when removing the shared SharePoint library in run-only permissions

Hi @RobMolenaar,

When you say “I try to disconnect the SharePoint library in the run-only permissions,” what exactly do you mean?

Could you please explain a bit more or share a screenshot for clarity?

I hope this information helps! If it does, please consider giving a 👍.

Best regards,
S-Venkadesh

Was this reply helpful? Yes No
RobMolenaar 112 on at

Like (0)

Report

ERROR when removing the shared SharePoint library in run-only permissions

Hi,

Sorry I wasn't clear.
In the Flow details, I click "Edit" next to "Run-only user." Then click on the trash can next to 'Currently shared with' and click Save

Was this reply helpful? Yes No
S-Venkadesh 861 Moderator on at

Like (0)

Report

ERROR when removing the shared SharePoint library in run-only permissions

Hi @RobMolenaar,

Based on the screenshot, it appears that the shared site has already been removed.

Therefore, the site ID is not visible in the run-only section. This could be a cache issue or an interruption during the delete process. Perhaps you can ignore it since it has already been removed.

I hope this information helps! If it does, please consider giving a 👍.
Best regards,
S-Venkadesh

Was this reply helpful? Yes No
RobMolenaar 112 on at

Like (0)

Report

ERROR when removing the shared SharePoint library in run-only permissions

I run many flows the same way with SharePoint. In all cases, I never see anything listed there, even if a SharePoint site is selected as Run-only users.

Was this reply helpful? Yes No
Suggested answer

GA-20111953-0 2 on at

Like (0)

Report

ERROR when removing the shared SharePoint library in run-only permissions

Hello!

I had the same issue and i solved it by adding the flow to a solution. After that i tried again to share the flow with a sharepoint list as run-only user and it worked fine for me.

Was this reply helpful? Yes No
RobMolenaar 112 on at

Like (0)

Report

ERROR when removing the shared SharePoint library in run-only permissions

Unfortunately, I can't put the flow in a solution because I'm using the For a selected file trigger (which I still find very unfortunate that it's not possible!).

Update 12/01:

I want to let you know that the problem has suddenly been resolved. I suspect it was a bug.

Was this reply helpful? Yes No