Skip to content

AFTER ignores named jobs that don't generate a cronstamp #29

@DNied

Description

@DNied

If job Y is waiting on job X (AFTER=X) but job X (ID=X) does not generate a cronstamp (because it's not scheduled via FREQ, but via the "classic" fields), then job Y is never executed.

This is undocumented behaviour (and IMHO counter-intuitive). All jobs named with an ID should probably generate a cronstamp, regardless of the syntax with which they are scheduled.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions