Unable to process template language expressions

[PDG]

Hello! I have built an app for my company that takes variable inputs from powerapps, creates a sharepoint list item, and then uses information from that sharepoint list item to populate a microsoft word template. This flow has worked on and off since I first started using it. The flow has worked upwards of 50 times in a row before failing, or it may fail the first or second attempt, but inevitably, the flow will fail with the following error:

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

I have fixed this error by recreating the flow from scratch, but exporting it and importing it as a new flow, and even just importing it as an update to an existing flow. The flow will work for a few minutes, or a few days, but again, it will inevitably fail for seemingly no reason.

Recreating the flow or reuploading it cannot be a long-term solution, because I can't spend time on this every day, and the app provides timely documentation to employees for deliveries. If I have to stop them for half an hour to fix this, it's simply not going to be feasible to use. Sometimes I have to re-upload the flow 4-5 times before it works, taking upwards of 30+ minutes to fix each time. I am now 'fixing' this issue almost every day. 

I have gone so far as to remove all of the variables within the flow being added to the template file and it still prevails with the same error. I've even observed that the flow will fail with one of the 'populate word document template' action, but succeed on both other 'populate word document template' action.

Is there a real solution to this error besides re-importing or recreating? Is there a real understanding of why this happens and what I can do to limit it's occurrence or work around it?

[v-bacao-msft · Accepted solution]

Hi @PDG ,

If you changed the configuration of the Flow which using the PowerApps button as the trigger, you need to remove the flow from the app and re-add it again.

Then this error will be solved. Please take a try again and feel free to let us know if the issue still exists.

Best Regards,

[PDG]

Thank you for the reply. Re-adding the flow to Powerapps has no impact on functionality unfortunately. The only way I've had success with this is by re-creating or re-importing the flow first.

[PDG]

Well, I gotta mark this as solved because it's working for now. I went back and re-added it to my flow for probably the 10th time today and it's worked. That being said, this time I simplified the process. Typically I would re-import the flow itself, and then re-add it in powerapps, but I didn't pay particular attention to the steps I took to update powerapps with the most recent version.

I think you're right that this all just stems from changes in the flow that aren't then reflect within powerapps, even though the flow has the same name and same input in powerapps. I had to remove the flow from the button, save the app, re-open the app, and then add the flow back to the button. Even flows that had failed only a few moments before are now working.

What's incredibly odd about this solution is what it entails for troubleshooting...  how have all of my other flows across all of my other apps not failed in similar ways due to making changes without updating the flow in powerapps.

This has been a strange one... and hopefully, I am done with it. Thank you for your help.

[PDG]

I should also mention that the cause of this error is also a bit up in the air. I understand the idea behind the stated cause, that if you change something in the flow without updating it in powerapps, the flow then displays the error (that also being the basis of our solution here).

Yet, the majority of the time it has broken so far, I have not been involved in the flow's configuration for some time.  In fact, I hadn't modified this flow in 3 days (since Friday) and it was in use all day Saturday without issue until it ran into issues this morning. I have a feeling there may be multiple causes for the issue.

[PDG]

Is there a way to remove the solution from a thread. This issue returned this morning without any further changes when being used on a refreshed version of the app. As I suspected, this solution doesn't stick.