Skip to content

bug: workflow scheduler omits global workflows #2260

Description

@oxoxDev

Summary

The workflow scheduler enumerates only a company's seed files and saved overlays. A workflow that exists only in the global baseline is therefore invisible to the scheduler, so any cron on that graph never fires and produces no diagnostic.

The scheduler should enumerate through the globals-aware listing while preserving company graph precedence, the per-workflow schedule switch, and [globals].disable opt-outs.

The currently shipped weekly_review cron must not be activated as part of this fix. Its schedule should be removed while the enumeration defect is corrected; activating that recurring, billed, owner-delivered workflow requires separate staging validation and review.

Reproduction

  1. Register a company with no seed or overlay workflows.
  2. Provide a global workflow with a valid trigger schedule matching the current tick.
  3. Tick the workflow scheduler.
  4. Observe that zero runs start because list_workflows_union cannot see the global baseline.

Expected behavior

The scheduler discovers scheduled global workflows through the globals-aware listing, skips globals named by the company's [globals].disable, and uses a same-id company workflow once instead of also listing the global.

Activity

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

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingpriority: p1Next. Wrong behaviour a user will hit, or a security weakness behind a condition.

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions