Azure logic App Run history filters are buggy - new experience

Question

in the Azure logic app run history section , the failed filter doesnt work(show no records even though there are Failed transaction, I have to select on failed then apply the filter, then it shows up ).

the customer date selection , fromDate and time works but ToDate time is not getting selected .

Answer 1

Hi @Amit kumar Mahato ,

Welcome to Microsoft Q&A, and thank you for your question.

From your description, both behaviors—the Failed filter showing no results until you apply it a second time, and the To Date/Time field not accepting a value—appear to be related to the Azure portal interface rather than your Logic App itself.

The key observation is that the failed runs appear after applying the same filter a second time. If the runs were actually missing from the backend, reapplying the filter would not return them. This suggests the issue is likely related to the portal's client-side filter state.

To help identify the cause, could you please try the following steps?

1. Open the Azure portal in an InPrivate/Incognito window

Open your Logic App in a private browser window (or perform a hard refresh using Ctrl + Shift + R) and then apply the Failed filter only once.

This helps clear any cached portal data that may be affecting the filter.

Expected result: The failed runs should appear the first time you apply the filter.

2. Refresh the Run History after applying the filter

After selecting the Failed filter, click the Refresh button on the Run History toolbar.

This forces the portal to request fresh data instead of displaying previously cached results.

Expected result: The failed runs should appear without needing to reselect the filter.

3. Verify the selected date range

Please ensure that the date range you're selecting is within your Logic App's run history retention period.

As a quick test, try filtering for the last 24 hours and check whether the failed runs are displayed.

Expected result: If runs appear within a shorter time range, the issue may be related to retention rather than the filter itself.

4. Query the run history using Azure CLI

To determine whether this is a portal issue, you can retrieve the failed runs directly through the Azure REST API:

az rest --method get --url "https://management.azure.com/subscriptions/<subscription-id>/resourceGroups/<resource-group>/providers/Microsoft.Logic/workflows/<workflow-name>/runs?api-version=2019-05-01&\$top=50&\$filter=Status%20eq%20'Failed'"

If this command returns the failed runs while the Azure portal does not, it confirms that the issue is with the portal interface rather than the Logic App service.

5. Check if a Legacy view option is available

Some Azure tenants still provide an option to switch back to the legacy Run History experience.

If you see this option, you can switch to it and verify whether the To Date/Time field behaves correctly.

If the option is not available, that is expected for many tenants, as the legacy experience has been retired in several regions.
Note:

If your Logic App is a Standard Logic App running a stateless workflow, run history is not stored unless it has been explicitly enabled. It would be worth confirming this as well, as it can also result in an empty run history.

If the assistance was helpful, kindly take a moment to click on Accept Answer and click on Yes. It will be helpful for other community members.

Answer 2

Dear Amit,

This appears to be a UI/filtering issue in the Azure Logic Apps Run History page. For the Failed status filter, the results do not load correctly unless the filter is manually selected and re-applied, suggesting a portal caching or filtering bug. For the custom date range, From Date/Time works as expected, but the To Date/Time value is not being retained or applied, which may be related to the same portal issue.

As a workaround, try using an InPrivate/Incognito browser session, clearing browser cache, or testing with a different browser. If the behavior persists, raise a Microsoft support ticket as this is likely a portal-side issue rather than a Logic App configuration problem.