@cfxlabsinc/b2b-services
    Preparing search index...

    One recent or upcoming action for a report schedule, flattened from Temporal's ScheduleDescription.info. outcome is only populated when the caller asks for run enrichment (a per-run workflow-execution describe); without it every past run is "started" because Temporal's schedule description only records that an action was taken, not how it finished.

    type ReportRun = {
        firstExecutionRunId: string;
        outcome:
            | "started"
            | "running"
            | "completed"
            | "failed"
            | "timed_out"
            | "canceled"
            | "terminated"
            | "continued_as_new";
        scheduledAt: Date;
        takenAt: Date;
        workflowId: string;
    }
    Index

    Properties

    firstExecutionRunId: string

    Run id of the first execution started by this action.

    outcome:
        | "started"
        | "running"
        | "completed"
        | "failed"
        | "timed_out"
        | "canceled"
        | "terminated"
        | "continued_as_new"

    Terminal outcome of the run. "started" until enriched; "running" for a currently-executing action; the rest map from Temporal workflow status.

    scheduledAt: Date

    Time the action was scheduled for (includes jitter).

    takenAt: Date

    Time the action was actually started.

    workflowId: string

    Temporal workflow id of the started run, rendered verbatim + copyable.