New Azure View Run History

Question

New Azure View Run History

Lily Nguyen 0

Azure automatically updated to the new view and now, I cannot view my run history. Every time I expand my "for loop" for inspection, the platform crashes.

Pravallika KV 16,605 Reputation points Microsoft External Staff Moderator

2026-06-03T19:46:07.52+00:00
Hi @Lily Nguyen ,

Here are a few things you can try to work around it and still get at your run details:

View your runs from the Overview blade

In the Azure portal, open your Logic App (Consumption) or Logic App (Standard) resource.

For Consumption apps: go to Overview → Runs history For Standard apps: open the designer, then under Tools → Run history

Pick the specific run you want to inspect.

Use the “Run details” list instead of expanding the tree

On the run history page, click Run details in the toolbar.

This shows each action (including your For Each) in a flat list. You can then click one iteration at a time rather than unfolding the entire loop at once.

Fetch details via REST or PowerShell/CLI

If the portal UI chokes on large loops, call the Logic Apps REST API to pull the run’s full JSON payload: GET /subscriptions/{sub}/resourceGroups/{rg}/providers/Microsoft.Logic/workflows/{workflow}/runs/{runId}?api-version=2016-06-01

Or use Get-AzLogicAppRunHistory in PowerShell / az logic workflow run show in CLI.

Ship your diagnostics to Log Analytics

Turn on diagnostic settings for your Logic App and send run events to a Log Analytics workspace.

Then run a Kusto query to pull out only the step(s) you need instead of overloading the UI.

Try a different browser or clear cache

Sometimes the new designer can misbehave if there’s stale UI state.

Test in an incognito/private window or switch browsers.

If you often loop over very large arrays, consider batching or filtering items so the portal doesn’t have to render hundreds of iterations at once.
Lily Nguyen 0 Reputation points

2026-06-03T22:10:01.3333333+00:00

I really want to be able to view the comments on the Run History tab. Every time I open run history the website crashes and the page becomes unresponsive. Is there any way I can go back to the old version of run history that worked?
Pravallika KV 16,605 Reputation points Microsoft External Staff Moderator

2026-06-06T00:35:29.6833333+00:00
Hi @Lily Nguyen ,

Unfortunately, there isn’t a “switch back” or toggle to the old UX Microsoft rolled the new view out globally and it’s not something you can opt out of. Once the old Logic Apps Run History experience has been retired for your tenant, users don't have a setting to permanently revert to it.

Why this is happening:

The new Run History UI is rendered in your browser.

Large For Each loops or complex runs can sometimes cause the new interface to freeze or crash.

This is usually a portal/UI issue, not a problem with your Logic App itself.

A few things are worth checking:

Check if there's a Preview/New Experience toggle (sometimes available, often not).

Try a different browser or an InPrivate/Incognito window.

If the issue persists, open a Microsoft Support case because this is likely a bug in the new portal experience.

1 answer

Your answer

Pravallika KV 16,605 Reputation points Microsoft External Staff Moderator

2026-06-03T19:46:07.52+00:00

Hi @Lily Nguyen ,

Here are a few things you can try to work around it and still get at your run details:

View your runs from the Overview blade

In the Azure portal, open your Logic App (Consumption) or Logic App (Standard) resource.

For Consumption apps: go to Overview → Runs history For Standard apps: open the designer, then under Tools → Run history

Pick the specific run you want to inspect.

Use the “Run details” list instead of expanding the tree

On the run history page, click Run details in the toolbar.

This shows each action (including your For Each) in a flat list. You can then click one iteration at a time rather than unfolding the entire loop at once.

Fetch details via REST or PowerShell/CLI

If the portal UI chokes on large loops, call the Logic Apps REST API to pull the run’s full JSON payload: GET /subscriptions/{sub}/resourceGroups/{rg}/providers/Microsoft.Logic/workflows/{workflow}/runs/{runId}?api-version=2016-06-01

Or use Get-AzLogicAppRunHistory in PowerShell / az logic workflow run show in CLI.

Ship your diagnostics to Log Analytics

Turn on diagnostic settings for your Logic App and send run events to a Log Analytics workspace.

Then run a Kusto query to pull out only the step(s) you need instead of overloading the UI.

Try a different browser or clear cache

Sometimes the new designer can misbehave if there’s stale UI state.

Test in an incognito/private window or switch browsers.

If you often loop over very large arrays, consider batching or filtering items so the portal doesn’t have to render hundreds of iterations at once.
Lily Nguyen 0 Reputation points

2026-06-03T22:10:01.3333333+00:00

I really want to be able to view the comments on the Run History tab. Every time I open run history the website crashes and the page becomes unresponsive. Is there any way I can go back to the old version of run history that worked?
Pravallika KV 16,605 Reputation points Microsoft External Staff Moderator

2026-06-06T00:35:29.6833333+00:00

Hi @Lily Nguyen ,

Unfortunately, there isn’t a “switch back” or toggle to the old UX Microsoft rolled the new view out globally and it’s not something you can opt out of. Once the old Logic Apps Run History experience has been retired for your tenant, users don't have a setting to permanently revert to it.

Why this is happening:

The new Run History UI is rendered in your browser.

Large For Each loops or complex runs can sometimes cause the new interface to freeze or crash.

This is usually a portal/UI issue, not a problem with your Logic App itself.

A few things are worth checking:

Check if there's a Preview/New Experience toggle (sometimes available, often not).

Try a different browser or an InPrivate/Incognito window.

If the issue persists, open a Microsoft Support case because this is likely a bug in the new portal experience.

Answer 1

The new run history experience in Azure Logic Apps can display and inspect runs, including actions inside loops, but there are known limitations around reruns and complex loop/concurrency scenarios.

For inspection and troubleshooting without expanding the loop in the portal:

Open the workflow’s run history instead of expanding the loop inline:
- For Consumption: In the Azure portal, open the logic app → Overview → Runs history, then select the specific run.
- For Standard (stateful workflows): In the workflow menu under Tools, select Run history, then select the run.
From the run details page, select the loop action itself (without expanding every iteration) to view high-level status and duration.
To inspect specific actions inside the loop without relying on the new UI expansion behavior, use diagnostics logging with Azure Monitor logs as described in the run-history documentation. This allows querying trigger, run, and action events (including loop iterations) outside the portal UI.

If the portal consistently crashes when expanding a For each loop:

Avoid using the “rerun from this action” feature on For each loops, as rerun support explicitly excludes For each actions and all actions inside and after the loop. Instead, rerun the entire workflow:
- Open Runs history → select the run → Resubmit.
If detailed per-iteration inspection is required, enable diagnostics logging to Azure Monitor logs and analyze the loop’s actions there rather than expanding the loop in the portal.
If the crash persists across browsers and sessions, capture the run’s Correlation Id from Run details and open a support ticket so the portal issue can be investigated with that identifier.

References:

Share via

New Azure View Run History

1 answer

Your answer