Skip to content

Block schedule enable when required secrets are unresolved #2257

Description

@federicodeponte

Problem

Manual runs already reject unresolved declared secrets before creating a run, but enabling a schedule does not perform the same preflight. A scheduled worker can therefore begin firing with a terminal configuration error.

Follow-up scope

  • Reuse the existing required-secret resolver when creating or enabling a schedule.
  • Return a structured 422 response listing missing secret names and connection requirements.
  • Preserve existing schedules when editing unrelated worker fields.
  • Add API and dashboard coverage for the blocker.

Context

Issue #2255 adds forward error-code instrumentation and an automatic circuit breaker after three consecutive scheduled terminal configuration failures. This issue moves detection earlier without expanding that focused fix.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions