'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Unable to Reach App Error for Power Automate Adaptive Cards in Teams
Question details
Users encounter an 'Unable to reach app' error in Microsoft Teams when a Power Automate flow attempts to send an adaptive card.
- Product
- Microsoft Teams and Power Automate
- Device & OS
- not provided
- Scenario
- Triggering a Power Automate flow to send an adaptive card to a Microsoft Teams channel or chat.
- Observed behavior
- The adaptive card fails to render or send, and Teams displays an 'Unable to reach app' error message in the chat.
Before troubleshooting, ensure you have active permissions for both the Power Automate environment and the destination Microsoft Teams channel or chat.
Verify Power Automate Connections and Adaptive Card Schema
Check for broken connections in your flow and ensure the JSON payload of your adaptive card is valid and supported.
Microsoft Teams restricts Adaptive Card formatting to specific versions (typically 1.4 or lower). An incorrect connection state or an incompatible JSON schema will directly result in an 'Unable to reach app' error when the flow executes.
Open your flow in Power Automate, navigate to the 'Connections' page, and verify that the Microsoft Teams connector is fully authenticated without any warning icons.
Review the Adaptive Card JSON schema within your flow action. Ensure the 'version' attribute is set to 1.4 or lower, as newer versions may not be fully supported by the Teams client.
Temporarily replace your complex adaptive card payload with a basic 'Hello World' Adaptive Card JSON to isolate whether the issue is caused by complex formatting or a general connectivity failure.
Go to the flow details page and select a failed run from the 28-day run history. Expand the Teams action step to review the raw inputs and outputs for specific HTTP error codes.
Escalate to the Microsoft Power Automate Community
If connection and schema checks pass but the error persists, consult the dedicated Power Platform support engineers.
Boost Your Productivity with WPS Office
While resolving Microsoft Teams and Power Automate integration errors, consider streamlining your daily document tasks with WPS Office. It's a lightweight, free, and highly compatible alternative to Microsoft Office that ensures seamless workflow without heavy resource usage.
- 1. Download the Installer: Visit the official WPS Office website and click on the 'Free Download' button for your operating system.
- 2. Install WPS Office: Run the downloaded setup file and follow the quick on-screen instructions to install the suite.
- 3. Open Your Office Files: Launch WPS Office and directly open any existing .docx, .xlsx, or .pptx files to continue working seamlessly.
Frequently Asked Questions
Why does Teams show 'Unable to reach app' for my Adaptive Card?
This error usually occurs due to expired connection credentials in the Power Automate Teams connector, an invalid JSON schema within your adaptive card, or insufficient permissions for the bot/user to post in the target Teams chat.
Which Adaptive Card version is supported in Microsoft Teams?
Microsoft Teams generally supports Adaptive Cards version 1.4 and earlier. Using features or schemas from newer versions in your Power Automate flow often results in rendering failures or connectivity errors.
How can I debug a failed Adaptive Card flow in Power Automate?
Navigate to your flow's details page, select a failed instance under the '28-day run history', and expand the Microsoft Teams action step. Reviewing the raw 'Inputs' and 'Outputs' will help you identify the exact JSON formatting error or HTTP status code.
