Repository navigation
Conversation
Prototype consumer of sentry.cadence to validate that its API covers scheduled Seer automations. Enabling an automation config schedules it daily, a Cadence firing records a cron-sourced SeerWorkflowRun deduplicated by its scheduled time, and config responses include nextRunAt. This is scheduling only, not Seer integration. Nothing is sent to Seer: each scheduled run records one empty placeholder execution and completes immediately. Candidate selection, dispatch via start_feature_run, and completion on result delivery are still to do.
github-actions
Bot
added
the
Scope: Backend
Preserve Cadence scheduling while Seer dispatch is unimplemented, without creating fake completed runs. Keep admission and deduplication ready for integration, with rollback if dispatch is enabled prematurely.
yuvmen
changed the title
trevor-e
approved these changes
Nov 10, 2026
This branch has not been deployed
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
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.
Connect Seer automation configs to Cadence. Enabled
AGENTIC_TRIAGE_V2configs get a daily schedule, synchronized when configs are created, updated, or deleted. Firings are spread over an hour and enqueue a task; config API responses exposenextRunAt.Execution is gated behind
organizations:seer-scheduled-automations. With the flag off, tasks log and return without creating run history. Run admission, snapshots, and deduplication are in place, but real Seer dispatch must be implemented before enabling the flag.This does not migrate or backfill existing legacy Night Shift configs.