Skip to content

execute() bypasses noOverlap / isBusy() tracking #611

Description

@jlssmt

Hey,

The core issue: getStatus() / isBusy() don't account for invoked (execute()) runs. The state machine only flips to 'running' when execution.reason === 'scheduled', so a manually invoked run is invisible to it.

That's also why noOverlap doesn't help here - it checks lastExecution's state, which relies on the same state machine. Fix getStatus() to track invoked runs too, and noOverlap should just work for execute() as a side effect.

Same behavior on 4.2.1 and 4.6.0.

Intentional, or worth a PR?

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions