Skip to content

Runs: deep link to a specific run fails when run is not on the first page #5345

@bender-rodriguez-unit1

Description

@bender-rodriguez-unit1

Problem

Copying a direct link to a run (e.g. ?view=runs&run=ea53b695-...) and opening it in a new tab does not open the specific run. The runs list loads the first page (~25 most recent runs) and tries to find the run ID in the loaded data. If the run is older and falls on page 2+, the frontend silently ignores the run param.

Steps to reproduce

  1. Open an app with many runs (100+)
  2. Scroll down in runs view and click on an older run
  3. Copy the URL from the browser
  4. Open the URL in a new tab
  5. The runs list shows but the specific run is not selected/opened

Expected

The specific run should be loaded and displayed, even if it is not on the first page.

Possible fix

When a run param is in the URL:

  1. Check if the run exists in the already-loaded page
  2. If not found, fetch the specific run by ID directly via the API
  3. Scroll to / highlight the run in the list (or paginate until found)

Same class of issue as the "See in Editor" button not working when a version is not yet loaded.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions