The behavior you're seeing is standard for SharePoint triggers. When a flow has Trigger Conditions that aren't met, the flow doesn't start at all, which is why your Run History remains empty.
1. Why "Manual Test" isn't working
For automated triggers like "When a file is created or modified," selecting Manual Test only puts the flow into a "listening" state. It does not force a run; it simply waits for an external SharePoint event to occur. If that event is filtered out by your conditions, the "listening" window will eventually time out with no result.
2. The Likely Culprit: Trigger Conditions
If the condition evaluates to false, the run is never instantiated.
Common issues: Null values in fields, incorrect case-sensitivity, or using internal field names that don't match your expression.
Quick Test: Temporarily remove all Trigger Conditions and save as suggested by
@Vish WR. Modify a file in SharePoint. If the flow runs, you know the logic error is inside your condition expression.
3. Check your "Split On" setting
In your trigger settings, Split On is likely unnecessary for this specific SharePoint trigger.
The Fix: Go to Settings and turn Split On = Off. If the trigger payload structure is being split incorrectly, it can prevent the flow from recognizing the event as a valid start.
4. Check for "Admin Mode"
If this is a Sandbox environment, ensure Admin Mode is disabled in the Power Platform Admin Center. When enabled, all background triggers are disabled, and only manual/instant flows will work.
Summary: The lack of Run History confirms the issue is at the Trigger level. Simplify the trigger by removing conditions and "Split On" to establish a baseline success, then add your logic back one step at a time.
