web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Adaptive Card step kil...
Power Automate
Suggested Answer

Adaptive Card step kills flow from triggering

(0) ShareShare
ReportReport
Posted on by
Hey all!

I have a flow that kicks off via Webhook when one of my Jamf policies finish. I actually have a few of these for different policies, they work great, no issues. However, I've recently had one flow just stop triggering, specifically when it has a step to post an Adaptive Card to a Teams channel. The card format (see below) is used exactly as it is in other flows, with some slight wording differences. If I take this step out, the flow triggers without issue. Put it back in, the flow never triggers. I have moderation in the Teams channel turned off, the JSON is using version 1.4, the variables called are all good, the Workflows app is installed in Teams, there's no waiting for a response for the post. I'm very much scratching my head here, since my other flows aren't having an issue.
Any thoughts?

Adaptive Card JSON:

{
    "type": "AdaptiveCard",
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "version": "1.4",
    "body": [
        {
            "type": "TextBlock",
            "wrap": true,
            "text": "A computer has been deployed!",
            "style": "heading",
            "fontType": "Default",
            "size": "large",
            "weight": "bolder"
        },
        {
            "type": "TextBlock",
            "wrap": true,
            "text": "The following computer has been deployed and updated inventory information in Jamf Pro and TDX:",
            "weight": "Default",
            "color": "Default",
            "size": "Default",
            "fontType": "Default",
            "style": "default"
        },
        {
            "type": "FactSet",
            "facts": [
                {
                    "title": "Computer Name",
                    "value": "@{variables('ComputerName')}"
                },
                {
                    "title": "Serial Number",
                    "value": "@{variables('SerialNumber')}"
                },
                {
                    "title": "Model",
                    "value": "@{body('Parse_JSON_Get_Jamf_Computer_Info')?['body']?['hardware']?['model']}"
                },
                {
                    "title": "macOS Version",
                    "value": "@{variables('macOSVersion')}"
                },
                {
                    "title": "IP Address",
                    "value": "@{variables('IPAddress')}"
                },
                {
                    "title": "Location",
                    "value": "@{variables('AssetLocation')}"
                }
            ]
        },
        {
            "type": "ActionSet",
            "actions": [
                {
                    "type": "Action.OpenUrl",
                    "title": "View Computer in Jamf Pro",
                    "url": "url scrubbed"
                }
            ]
        },
        {
            "type": "ActionSet",
            "actions": [
                {
                    "type": "Action.OpenUrl",
                    "title": "View Computer in TDX",
                    "url": "url scrubbed"
                }
            ]
        }
    ]
}
I have the same question (0)
  • Suggested answer
    SebS Profile Picture
    4,803 Super User 2026 Season 1 on at
    Did You try version 1.5 ?

    If I good remember Styles "Default", "Heading"  in TextBlock you are using is supported from 1.5 version it should not matter but who knows

     try move to version 1.5 check if it improve next test 

     move down to 1.2 version but remove 

    "style": "heading"
    "style": "default"

    from TextBlocks
  • Suggested answer
    11manish Profile Picture
    791 on at
    This strongly indicates the issue is with the Teams action initialization, not your trigger.
     
    If adding Teams Adaptive Card stops trigger →
    It’s usually connection or card validation issue
     
    Start with:
    • Re-authenticate Teams
    • Replace dynamic values
    • Recreate action
  • RM-02041250-0 Profile Picture
    on at
    Thank you both for your suggestions, they are very much appreciated! However, neither were successful in resolving the issue unfortunately.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Automate

#1
Haque Profile Picture

Haque 589

#2
Valantis Profile Picture

Valantis 328

#3
David_MA Profile Picture

David_MA 284 Super User 2026 Season 1

Last 30 days Overall leaderboard