Azure / Azure/LogicAppsUX

[New Experiment]: Feature request: Adding an auto refresh feature to the Run history for both Draft and Published versions.

Open
#8,822 8 comments 0 reactions 0 assignees View on GitHub
Feature Request Found By Testers Good First Issue
Dominant language
TypeScript
Stars
111
Forks
109
Avg merge
1d 23h
Merged PRs (30d)
20

Description

### Severity

P4 - Low (Cosmetic/minor inconvenience)

### Describe the Bug with repro steps

1. Create a standard Logic App.
2. Use the new experiment to create a workflow.
3. Add an HTTP request trigger and action of your choice
4. Publish the workflow
5. Go to the run history tab in either the draft or published version.
6. Click on run button

**Expected:** The run history should automatically update with new runs in both draft and published versions. Adding an auto-refresh feature for the run history, set to refresh after a certain number of seconds, could help improve the user experience.

**Actual:** The run history does not automatically refresh with new runs in either draft or published versions. We have to manually click refresh button to see the latest run every time.

### What type of Logic App Is this happening in?

Standard (Portal)

### Are you experiencing a regression?

New feature so not a regression

### Which operating system are you using?

Windows

### Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

### Workflow JSON

```json

```

### Screenshots or Videos

_No response_

### Environment

Edge,

Issue repro in canary test pass
**Version:** 2.0.20260217.1

### Additional context

_No response_

Contributor guide

No contributing guide indexed for this repository

Research direction

No file or test is named. Start at the Run history tab implementation and trace the existing manual refresh behavior for both Draft and Published versions. Done means new runs appear automatically in both views after a defined refresh interval without requiring the button.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.