Action in a Flow suddenly throws error

(0) Share

Report

Posted on by heldry

I did some small changes in a Flow on an action that sends an email.

After saving the Flow a total unrelated action (that gets a SharePoint list item) is throwing this error.

Unable to process template language expressions in action 'Get_item' inputs at line '1' and column '2234': '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 'shared_sharepointonline, shared_office365'. Please see https://aka.ms/logicexpressions for usage details.'.

The strange thing is:

did not touch that Get SharePoint Item action ... it just started throwing the error without changes by me
have no way to set/change/influence the value 'shared_sharepointonline_1'
deleted the action and recreated it and end up with the same error

How can I get my Flow working again, please ?

Categories:

Using flows

I have the same question (0)

All responses (4)

Answers (1)

Jcook 7,781 Most Valuable Professional on at

Like (0)

Report

Hello @heldry

Can you try:

- Remove the SharePoint action and than re create.

- Create a New SharePoint connection, this can be done by clicking on the email that shows up on the action in the bottom right corner, than clicking change connection.

- If none of those suggestions work. Try creating a basic flow with SharePoint action and run it as a test.

Was this reply helpful? Yes No
v-bacao-msft on at

Like (0)

Report

Hi @heldry ,

Are you using the PowerApps button as the trigger?

If yes, after you edited the flow, you need to remove the flow from the specified app and re-add it again, then this error will be solved.

Please take a try and check if the issue still exists.

Best Regards,

Was this reply helpful? Yes No
heldry 32 on at

Like (0)

Report

Hi Barry,

yes, the PowerApps button is the trigger for the Flow.

As per your advise I removed the connection to the Flow from PowerApp and added it again ... and everything is fine now 🙂

But I'm honesly struggling to understand why updating one action in a Flow triggers that issue and why re-creating the connection in PowerApps fixes the Flow issue. Can you please share more background on this.

Was this reply helpful? Yes No
Verified answer

v-bacao-msft on at

Like (0)

Report

Hi @heldry ,

Please check this article and get more details about it:

https://support.microsoft.com/en-us/help/4477072/best-practices-updating-a-flow-used-by-a-powerapp

Best Regards,

Was this reply helpful? Yes No