Member Junction
    Preparing search index...

    Execute Scheduled Job Now action.

    Runs a scheduled job immediately, bypassing its cron schedule, through the same engine path the poller uses — lock acquisition, plugin execution, the run record, statistics, and notifications.

    This used to write a Status='Running' run row and return. Nothing consumed those rows: there is no queue reader for ad-hoc runs, only the cron poller, which selects jobs by their schedule and never looks at pending run records. So "Execute Now" reported success, left a row that said Running forever, and never ran anything. Delegating to SchedulingEngine.ExecuteScheduledJob is what makes the name true.

    await RunAction({
    ActionName: 'Execute Scheduled Job Now',
    Params: [
    { Name: 'JobID', Value: 'F3C4A5B6-...' }
    ]
    });

    Hierarchy (View Summary)

    Index

    Constructors

    Methods

    • Build filter expression for job queries

      Parameters

      • filters: {
            createdAfter?: Date;
            createdBefore?: Date;
            isActive?: boolean;
            jobTypeId?: string;
            status?: string;
        }

        Object containing optional filter criteria

      Returns string

      SQL WHERE clause string

    • Runs a scheduled job immediately.

      Parameters

      • params: RunActionParams

        The action parameters containing:

        • JobID (required): ID of the job to execute
        • Wait (optional, default true): await the job and report its real outcome. Set false to start it and return as soon as it is under way — useful for a long job behind an interactive button, at the cost of the result only saying it started.

      Returns Promise<ActionResultSimple>

      ActionResultSimple with:

      • Success: whether the job itself succeeded (or, with Wait=false, whether it started)
      • ResultCode: SUCCESS, VALIDATION_ERROR, NOT_FOUND, LOCKED, JOB_FAILED, STARTED, or FAILED
      • Params: output parameters 'RunID' and 'RunStatus'