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 / Split On In Power Auto...
Power Automate
Answered

Split On In Power Automate Trigger

(0) ShareShare
ReportReport
Posted on by 169
I have a Flow using Sharepoint.  It is triggered When an item is created or modified.
The user can make several updates per minute, so it is missing triggers.
I tried putting the Split on, but it didn't run at all.  The split array is triggerbody()?['value'] which is the only available value in the drop down and I can't manually change it.
There is no tracking ID.
It has a trigger condition @equals(triggerBody()?['value']?[0]?['AdjustmentStatus']?['Value'], 'New')
 
How can I write a Flow to cope with multiple updates per minute?
Categories:
I have the same question (0)
  • Verified answer
    deepakmehta13a Profile Picture
    369 on at

    Hi,

    A few key points:

    1. Split On is not applicable here
      “Split On” works when the trigger returns an array (like HTTP or batch responses).
      The SharePoint trigger returns one item per event, so using:
      triggerBody()?['value']
      won’t work and can stop the trigger from firing.

    2. Why updates are getting missed
      The SharePoint trigger uses polling, so if multiple updates happen quickly, some events can be skipped or merged.

    3. Recommended approach:

    Option 1 – Use trigger conditions properly
    Instead of indexing like [0], use:

    @equals(triggerBody()?['AdjustmentStatus']?['Value'], 'New')

    This ensures the trigger evaluates the current item correctly.

    Option 2 – Enable concurrency control

    • Go to trigger settings

    • Turn ON concurrency

    • Set degree (e.g., 1–5 depending on load)

    This helps process multiple updates more reliably.

    Option 3 – Add delay / queue pattern (more robust)

    • Trigger flow on change

    • Store item ID in a queue (SharePoint list / Dataverse)

    • Process updates in a separate flow

    This avoids missing rapid updates.

    Option 4 – Use “Get changes for an item”
    Track changes using versioning and process based on actual field changes instead of relying only on trigger timing.

    1. Important
      Remove “Split On” — it is not needed for this trigger and is causing the issue.

    Hope this helps.

    If this helps resolve your issue, please consider marking the response as Verified so it can help others facing a similar scenario.

    If you found this helpful, you can also click “Yes” on “Was this reply helpful?” or give it a Like.

  • Suggested answer
    11manish Profile Picture
    3,333 on at
    In Microsoft Power Automate, the SharePoint trigger “When an item is created or modified” is not reliable for frequent updates, so some changes may be missed.

    Key issues
    • SharePoint triggers are throttled and batched
    • Multiple updates per minute → missed triggers
    • Split On does not apply (not an array trigger)
    • Your trigger condition should be simplified (no value[])
    Best approach
    Use a more reliable pattern:
    • Trigger fires
    • Add Delay (10–30 sec)
    • Use Get item / Get changes
    • Check latest value before processing

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

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Valantis Profile Picture

Valantis 377

#2
11manish Profile Picture

11manish 279

#3
David_MA Profile Picture

David_MA 234 Super User 2026 Season 1

Last 30 days Overall leaderboard