We really scratched our heads on this one!! We have a very complex flow with many switches which send email approvals from our PowerApp. It was working great for a while. After our latest round of change, it started failing only sometimes, and the error that was thrown:
Unable to process template language expressions in action 'New_Reminder_Service_Offer_to_SVP_Approval' inputs at line '1' and column '1943': 'The template language expression 'json(decodeBase64(triggerOutputs().headers['X-MS-APIM-Tokens']))['$connections']['shared_office365_2']['connectionId']' cannot be evaluated because property 'shared_office365_2' doesn't exist, available properties are 'shared_office365'. Please see https://aka.ms/logicexpressions for usage details.'.
We searched and could NOT find what was causing this! FINALLY WE LEARNED, through a thought of hard work and stupefied brain power, about a quirk. We had multiple authors working in the flows (one at a time so we did not step over each other). It turns out, the Connector for the Primary Author was the only one that would connect to Outlook (only the primary connector could send emails from Outlook).
FIX: For Each EMAIL SEND connector, Click the Elipsis in the header of the connector and switch the connection to the email of the PRIMARY AUTHOR.
Note: Exporting the Flow and Re-importing to another environment strips the muliple connections and only the Outlook Connection for the current user will remain. (for migrating to Production).
Solved! Go to Solution.