Severity
P2 - High (Major functionality broken)
Describe the Bug with repro steps
Description
In the new Azure Logic Apps designer experience, the Run History filtering does not work correctly when using a custom time range.
Specifically, selecting an End time has no effect, resulting in incorrect or empty run history results.
Reproduction Steps
Open Azure Portal
Navigate to a Logic App (Consumption)
Example: wcc-dev-salesforce-process-creation-common-logic
Go to Run history tab (new experience)
Apply filters:
Time range: Custom range
Set:
From date/time
To date/time (End time)
Observe the results
Expected behaviour
Run history should be filtered correctly based on both:
Start time
End time
Results should only include runs within the selected time range
Actual behaviour
Changing the End time has no effect
Results are either:
Not filtered correctly, or
Show “No runs found” even when runs exist
Filtering behaviour is inconsistent/unreliable
🔷 Impact
- Unable to reliably filter run history
- Slows down troubleshooting of Logic Apps
- Forces users to switch back to legacy experience
What type of Logic App Is this happening in?
Consumption (Portal)
Are you experiencing a regression?
No response
Which operating system are you using?
Windows
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
Screenshots or Videos
Environment
Region: UK South (or your actual region)
Logic App Type: Consumption
Browser: Chrome (latest)
OS: Windows 11
Experience: New Logic Apps Designer (Consumption V2 / React View)
Additional context
Issue occurs only in the new Logic Apps experience (React-based UI)
Switching to previous experience works correctly (confirmed)
Happens consistently across multiple attempts
Impacts troubleshooting and operational monitoring of runs
Severity
P2 - High (Major functionality broken)
Describe the Bug with repro steps
Description
In the new Azure Logic Apps designer experience, the Run History filtering does not work correctly when using a custom time range.
Specifically, selecting an End time has no effect, resulting in incorrect or empty run history results.
Reproduction Steps
Open Azure Portal
Navigate to a Logic App (Consumption)
Example: wcc-dev-salesforce-process-creation-common-logic
Go to Run history tab (new experience)
Apply filters:
Time range: Custom range
Set:
From date/time
To date/time (End time)
Observe the results
Expected behaviour
Run history should be filtered correctly based on both:
Start time
End time
Results should only include runs within the selected time range
Actual behaviour
Changing the End time has no effect
Results are either:
Not filtered correctly, or
Show “No runs found” even when runs exist
Filtering behaviour is inconsistent/unreliable
🔷 Impact
What type of Logic App Is this happening in?
Consumption (Portal)
Are you experiencing a regression?
No response
Which operating system are you using?
Windows
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
Not Applicable.Screenshots or Videos
Environment
Region: UK South (or your actual region)
Logic App Type: Consumption
Browser: Chrome (latest)
OS: Windows 11
Experience: New Logic Apps Designer (Consumption V2 / React View)
Additional context
Issue occurs only in the new Logic Apps experience (React-based UI)
Switching to previous experience works correctly (confirmed)
Happens consistently across multiple attempts
Impacts troubleshooting and operational monitoring of runs