- Add replayed_from_friendly_id column to ClickHouse task_runs_v2 table
- Create migration 012_add_task_runs_v2_replayed_from.sql
- Update replication service to include the new field
- Add getRunReplays query to ClickHouse client (optimized with org/project/env filter)
- Update SpanPresenter to query replays from ClickHouse
- Add "Replayed as" section in run Details tab showing linked replay runs with status
The ClickHouse query filters by organization_id, project_id, and environment_id
in the correct order to match the primary key for optimal query performance.
This enables users to see which runs have been replayed from the original run,
addressing the feedback about tracking replay status of failed runs.
Slack thread: https://triggerdotdev.slack.com/archives/C045W9WM3E1/p1767609682537389
Claude
432c3601bc