Skip to content

Handle "expected" cron errors #2

@WPprodigy

Description

@WPprodigy

Errors like Error: No resources available to run the job with action... will occur when a job is attempted to be run but application-level currency locks stopped it and returned early.

This is not a true error, as it's expected to some degree. So we should better handle these, and perhaps provide a more customized metric for keeping an eye on them.

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