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 / Regression in Teams tr...
Power Automate
Unanswered

Regression in Teams trigger for new channel messages

(0) ShareShare
ReportReport
Posted on by Microsoft Employee
 
 
 
 
 

There is a regression in the trigger for Teams, on any of the kind the triggers when a new channel message or message is received. Last successful run was 2/23. Since then it fails with an ISO date issue.

 

 

 

 

 

 

Unable to compute iso trigger state.

Categories:
I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    479 on at
    Hi,

    Can you share screenshots of your Power Automate configuration and share the exact error message you are getting?
  • MP-04030319-0 Profile Picture
    Microsoft Employee on at
    Hi Andre, 
     
    Seems like the image didn't load correctly in the original message. Here they are:

    Summary:

    Error:

    Unable to compute iso trigger state

     

    What’s happening:
    The workflow fails while computing the latest message timestamp from a set of Microsoft Teams channel messages. During evaluation, one of the date fields cannot be parsed as a valid DateTime, causing the trigger state calculation to fail.

     

    Root cause (likely):
    A malformed or unexpected date/time value is present in the message payload (e.g. createdDateTime or a derived field). The exception is thrown when the logic attempts to:


    • Convert a string to DateTime
    • Apply a LINQ Max() operation over the message timestamps


    •  
    •  

    Exception details:

    System.FormatException: String was not recognized as a valid DateTime
     at System.Convert.ToDateTime(String value)
     at Newtonsoft.Json.Linq.JToken.op_Explicit
     at System.Linq.Enumerable.Max(...)
    
     

    Context:


    • Messages come from a Teams channel with repeated posts (same PR review message sent multiple times).
    • At least one item appears to contain an invalid or improperly encoded date string (e.g. URL‑encoded timestamp or unexpected format).
    • This breaks the ISO trigger state evaluation, preventing the flow from progressing.


    •  
    •  
     

    Impact:


    • Teams trigger fails intermittently or consistently
    • Flow does not advance or evaluate new messages
    • Trigger state cannot be computed

    •  

    Suggested investigation areas:


    • Validate all createdDateTime / lastModifiedDateTime values before conversion
    • Guard Max() logic against null/invalid date value
    • Confirm whether any message metadata includes URL‑encoded or non‑ISO date strings






    Error message (obfuscated):

    Unable to compute iso trigger state.

    Items:
    [
    {
    "replyToId": null,
    "etag": "<ETAG>",
    "messageType": "message",
    "createdDateTime": "<ISO_DATETIME>",
    "lastModifiedDateTime": "<ISO_DATETIME>",
    "lastEditedDateTime": null,
    "deletedDateTime": null,
    "subject": "<SUBJECT>",
    "summary": null,
    "chatId": null,
    "importance": "normal",
    "locale": "en-us",
    "webUrl": "<TEAMS_MESSAGE_URL>",
    "onBehalfOf": null,
    "policyViolation": null,
    "eventDetail": null,
    "id": "<MESSAGE_ID>",
    "from": {
    "application": null,
    "device": null,
    "user": {
    "@odata.type": "#microsoft.graph.teamworkUserIdentity",
    "id": "<USER_OBJECT_ID>",
    "displayName": "<USER_NAME>",
    "userIdentityType": "aadUser",
    "tenantId": "<TENANT_ID>"
    }
    },
    "body": {
    "contentType": "html",
    "content": "<MESSAGE_HTML_CONTENT>"
    },
    "channelIdentity": {
    "teamId": "<TEAM_ID>",
    "channelId": "<CHANNEL_ID>"
    },
    "attachments": [],
    "mentions": [],
    "reactions": []
    }
    ]

    Exception:
    System.FormatException: String was not recognized as a valid DateTime.
    at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles)
    at System.Convert.ToDateTime(String value, IFormatProvider provider)
    at Newtonsoft.Json.Linq.JToken.op_Explicit(JToken value)
    at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
    at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
    at System.Linq.Enumerable.MaxIEnumerable`1 source
    at <EXPRESSION_CONTAINER>.Expression_<ID>(IProxyRequestContext context)
  • André Arnaud de Calavon Profile Picture
    479 on at
    Thanks for sharing the error details. Can you also share the details of your flow and a screenshot on what action the flow run stops?
  • MP-04030319-0 Profile Picture
    Microsoft Employee on at
    Yes, the flow is for automatic replies to questions in a support Teams Channel. The flow fails immediately on the trigger. Even when changing the channel, duplicating the flow or starting a new one with that trigger, the process fails.






  • LF-13031712-0 Profile Picture
    Microsoft Employee on at
    I am experiencing the exact same issue. Is there a mitigation for this? Any work around I can use?
  • André Arnaud de Calavon Profile Picture
    479 on at
    Hi,

    If you keep experiencing this issue, I suggest you creating a ticket for Microsoft Support. This indeed looks like a regression.
     
     
  • MP-04030319-0 Profile Picture
    Microsoft Employee on at
    Could you please share the link to create the ticket?

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 286

#2
David_MA Profile Picture

David_MA 256 Super User 2026 Season 1

#3
Expiscornovus Profile Picture

Expiscornovus 225 Most Valuable Professional

Last 30 days Overall leaderboard