Skip to content

Add streaming to workflow evaluation run detail page#6183

Open
simeonlee wants to merge 1 commit intomainfrom
simeonlee/wf-eval-streaming-run-detail
Open

Add streaming to workflow evaluation run detail page#6183
simeonlee wants to merge 1 commit intomainfrom
simeonlee/wf-eval-streaming-run-detail

Conversation

@simeonlee
Copy link
Member

@simeonlee simeonlee commented Feb 5, 2026

Summary

  • Add Suspense/Await streaming to the workflow evaluation run detail page
  • Show run ID in header immediately while data loads
  • Extract fetchRunData helper with all data fetching logic
  • Add skeleton and error states with consistent headers
  • Use useSearchParams instead of window.location.search
  • Fix != to !== for strict equality

Test plan

  • Verify run ID shows in header immediately while content loads
  • Verify skeleton state shows while loading
  • Verify error state displays correctly (e.g. invalid run ID)
  • Verify pagination works
  • Run e2e tests: pnpm test-e2e

Note

Low Risk
UI-only refactor to async rendering and pagination URL handling; main risk is regressions in loading/error states and offset navigation.

Overview
Streams the workflow evaluation run detail page by returning a deferred runData promise from the loader and rendering it via Suspense/Await, so the run ID header shows immediately while data loads.

Extracts fetching into fetchRunData and adds dedicated skeleton and error states (with consistent header + SectionErrorNotice). Pagination now uses useSearchParams instead of window.location.search, and a strict equality check replaces != with !==.

Written by Cursor Bugbot for commit dba7819. This will update automatically on new commits. Configure here.

Defer all data loading behind a single Suspense boundary. The page
header shows the run ID from route params immediately while data loads.
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

description={message}
/>
</>
);
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Duplicated error message extraction logic

Low Severity

The ContentError function manually extracts error messages using isRouteErrorResponse and instanceof Error checks. This duplicates the existing getErrorMessage utility from ~/components/ui/error/ErrorContentPrimitives which provides the same functionality. Using getErrorMessage({ error, fallback: "Failed to load workflow evaluation run" }) would be cleaner.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant