feat(seer): Return sentry_run_id from runs list and dashboard generate#117808
Merged
trevor-e merged 2 commits intoJun 16, 2026
Merged
Conversation
Surface the run's UUID on the two remaining endpoints that only returned the numeric run id: - GET /seer/explorer-runs/ adds sentry_run_id per run (single bulk SeerRun lookup; null for legacy runs with no mirror row). - POST /dashboards/generate/ returns sentry_run_id alongside run_id. Additive: existing clients ignore the new field.
github-actions
Bot
added
the
Scope: Backend
Build the runs-list items via an AgentRunWithUuid(AgentRun) subclass instead of spreading into a raw dict, keeping AgentRun pure (it models Seer's response) and the sentry_run_id enrichment at the API layer. Type the dashboard-generate response with a DashboardGenerateResponse model. Same wire shape; mypy now knows both response shapes.
NicoHinderling
approved these changes
Jun 16, 2026
trevor-e
deleted the
telkins/feat-seer-return-uuid-runs-list-and-dashboard
branch
billyvg
pushed a commit
that referenced
this pull request
Jun 17, 2026
#117808) Surfaces the run's UUID (`sentry_run_id`) on two more Seer endpoints that only returned the numeric run id, matching explorer chat, search agent, and autofix. - `GET /seer/explorer-runs/` adds `sentry_run_id` per run via a single bulk `SeerRun` lookup (`null` for legacy runs with no mirror row). - `POST /dashboards/generate/` returns `sentry_run_id` alongside `run_id`. Purely additive — existing clients ignore the new field. Not covered here: - `project_seer_night_shift.py` — its `SeerRun` isn't mirrored at all (created outside the outbox); needs the deeper outbox-mirroring fix, tracked separately. - `organization_seer_agent_pr_groups.py` — still returns a numeric-only run id. - Frontend adoption (sessions-list picker preferring the UUID, dashboards `from-seer` flow) is separate.
sehr-m
pushed a commit
that referenced
this pull request
Jun 23, 2026
#117808) Surfaces the run's UUID (`sentry_run_id`) on two more Seer endpoints that only returned the numeric run id, matching explorer chat, search agent, and autofix. - `GET /seer/explorer-runs/` adds `sentry_run_id` per run via a single bulk `SeerRun` lookup (`null` for legacy runs with no mirror row). - `POST /dashboards/generate/` returns `sentry_run_id` alongside `run_id`. Purely additive — existing clients ignore the new field. Not covered here: - `project_seer_night_shift.py` — its `SeerRun` isn't mirrored at all (created outside the outbox); needs the deeper outbox-mirroring fix, tracked separately. - `organization_seer_agent_pr_groups.py` — still returns a numeric-only run id. - Frontend adoption (sessions-list picker preferring the UUID, dashboards `from-seer` flow) is separate.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Surfaces the run's UUID (
sentry_run_id) on two more Seer endpoints that only returned the numeric run id, matching explorer chat, search agent, and autofix.GET /seer/explorer-runs/addssentry_run_idper run via a single bulkSeerRunlookup (nullfor legacy runs with no mirror row).POST /dashboards/generate/returnssentry_run_idalongsiderun_id.Purely additive — existing clients ignore the new field.
Not covered here:
project_seer_night_shift.py— itsSeerRunisn't mirrored at all (created outside the outbox); needs the deeper outbox-mirroring fix, tracked separately.organization_seer_agent_pr_groups.py— still returns a numeric-only run id.from-seerflow) is separate.