Unanswered

Flow fails for users, works for flow creator

(0) Share

Report

Posted on by Spinner

124

For no apparent reason, a flow has started failing when triggered by any user other than the flow creator (me). When I run it, no errors appear; when another user runs it, it fails with this message:

Unable to process template language expressions in action '*********' inputs at line '1' and column '2447': 'The template language expression 'json(decodeBase64(triggerOutputs().headers['X-MS-APIM-Tokens']))['$connections']['shared_sharepointonline_1']['connectionId']' cannot be evaluated because property 'shared_sharepointonline_1' doesn't exist, available properties are 'fileSource'. Please see https://aka.ms/logicexpressions for usage details.'.

The flow itself is simple - it gets a set of files in a SharePoint library that match a specific condition and returns the number to PowerApps.

I've tried setting up a new version of the flow but with no success.

Has anyone else had similar issues? Is this a Microsoft problem?

Categories:

Using flows

All responses (4)

Answers (0)

Sort by

Spinner 124 on at

Like
a
(0)

Report
Copy link

Link copied!

It's also bizarre that that the flow still works for me even if I delete all the SharePoint connections that it uses.
alrezac Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,

Manual flow triggers like this one will use the permissions of the user running the flow. So if the users running this flow are unable to navigate to the file that is being gotten in the get action then it will fail. At this point you would need to give permissions to all the users who would run this flow access to the file too.

Regards,

Alex

-------

Community Support Team _ Alex Rezac
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Spinner 124 on at

Like
a
(0)

Report
Copy link

Link copied!

@alrez Thanks for the reply, Alex.

All the users have access to the SharePoint library whose items are being accessed in the get action. The library is listed as an owner of the flow. The flow was working up to yesterday and abruptly stopped working for no obvious reason; there have been no changes in permissions.
Spinner 124 on at

Like
a
(0)

Report
Copy link

Link copied!

@alrez I've just seen this thread reporting what sounds like a similar issue that has, like ours, just cropped up in the last day or so. Our flow is, like the one mentioned there, launched via PowerApps, though in our case a PowerApps customised form: https://powerusers.microsoft.com/t5/Building-Power-Apps/PowerApps-calling-PowerAutomate-flow-stopped-working-for-all/m-p/855049