Member Junction
    Preparing search index...

    Interface TelemetryRunViewsBatchParams

    Telemetry params for batch RunViews operation. Used when multiple views are executed in a single call.

    interface TelemetryRunViewsBatchParams {
        _fromEngine?: boolean;
        BatchSize: number;
        Entities: string[];
        Exempt?: boolean;
        ExemptReason?: string;
        Filters?: string[];
        OrderBys?: string[];
    }
    Index

    Properties

    _fromEngine? BatchSize Entities Exempt? ExemptReason? Filters? OrderBys?

    Properties

    Optional_fromEngine

    _fromEngine?: boolean

    Internal marker for engine-initiated calls

    BatchSize: number

    Number of views in the batch

    Entities: string[]

    Entity names being queried in the batch

    Exempt?: boolean

    When true, every view in the batch opted out of optimization/redundancy analyzers.

    ExemptReason?: string

    Optional caller-provided justification for the exemption (first non-empty across the batch).

    Filters?: string[]

    Per-view SQL WHERE clause filters, parallel to Entities (one entry per view, same order). Populated where the batch event is recorded so the fingerprint can distinguish two batches over the SAME entity set but with DIFFERENT filters (e.g. an expiry sweep vs. a decay sweep both over {AI Agent Notes, AI Agent Examples}). An entry may be undefined when a view supplied no filter.

    OrderBys?: string[]

    Per-view SQL ORDER BY clauses, parallel to Entities (one entry per view, same order). See Filters for why per-view detail is needed at batch granularity.

    Settings

    Member Visibility

    On This Page

    Properties