Member Junction
    Preparing search index...

    PERSISTENCE seam — records run lifecycle, per-record detail, checkpoints, and the pause/cancel handshake. The default GenericProcessRunTracker (in the engine package) writes MJ: Process Runs / MJ: Process Run Details; domain consumers can supply their own (e.g. the classifier's Content Process Runs), and NoOpTracker discards everything for fire-and-forget single-record work.

    interface IProcessRunTracker {
        BeginRun(
            meta: ProcessRunMeta,
            contextUser: UserInfo,
            provider?: IMetadataProvider,
        ): Promise<RunHandle>;
        Checkpoint(
            handle: RunHandle,
            cursor: ProcessCursor,
            counts: RunCounts,
            contextUser: UserInfo,
            provider?: IMetadataProvider,
        ): Promise<boolean>;
        CompleteRun(
            handle: RunHandle,
            summary: ProcessRunSummary,
            contextUser: UserInfo,
            provider?: IMetadataProvider,
        ): Promise<void>;
        LoadResumeCursor(
            handle: RunHandle,
            contextUser: UserInfo,
            provider?: IMetadataProvider,
        ): Promise<ProcessCursor>;
        RecordResult(
            handle: RunHandle,
            record: RecordRef,
            result: RecordResult,
            contextUser: UserInfo,
            provider?: IMetadataProvider,
        ): Promise<void>;
    }

    Implemented by

    Index

    Methods