Struct RunDetailResponse 

pub struct RunDetailResponse {

    pub id: i64,
    pub tag_name: String,
    pub notes: Option<String>,
    pub driver: TuneDriver,
    pub outcome: TuneOutcome,
    pub failure_reason: Option<String>,
    pub started_at: DateTime<Utc>,
    pub completed_at: Option<DateTime<Utc>>,
    pub template_name: String,
    pub template_origin: TemplateOrigin,
    pub allow_uncertain_quality: bool,
    pub config: LoopConfig,
    pub pid_rounding: PidRounding,
    pub effective_tuning: Option<EffectiveTuning>,
    pub opc_server: Option<String>,
    pub bridge_host: Option<String>,
    pub pid_constant_tags: Option<PidConstantTagsResponse>,
    pub pid_parameter_labels: PidParameterLabelsResponse,
    pub initial_readings: Option<InitialReadingsResponse>,
    pub timing_metrics: Option<TimingMetrics>,
    pub samples: Vec<SampleResponse>,
    pub results: Vec<ResultResponse>,
    pub writes: Vec<WriteResponse>,
    pub mv_actuations: Vec<MvActuationResponse>,
    pub restore_status: Option<RestoreStatus>,
    pub restore_detail: Option<String>,
    pub original_request: Option<StartRunRequest>,
    pub gateway_compatibility: Option<GatewayCompatibilityResponse>,
}

Fields

id: i64

tag_name: String

notes: Option<String>

driver: TuneDriver

outcome: TuneOutcome

failure_reason: Option<String>

started_at: DateTime<Utc>

completed_at: Option<DateTime<Utc>>

template_name: String

Name of the template snapshotted onto this run at start time – not necessarily what template_name currently resolves to in the catalog (safety-run-snapshot).

template_origin: TemplateOrigin

allow_uncertain_quality: bool

Whether this run accepted Uncertain OPC quality, captured when the run started.

config: LoopConfig

pid_rounding: PidRounding

Precision policy from the run’s immutable template snapshot.

effective_tuning: Option<EffectiveTuning>

Concrete global timing and safety values frozen when this run was prepared. None identifies a run created before effective-tuning snapshots were stored.

opc_server: Option<String>

The resolved OPC DA server ProgID this run actually used, or None for a simulator/replay run (db-run-request-snapshot). This is what history revert trusts over any --server flag – see bhtune_runtime::history::revert_run.

bridge_host: Option<String>

The resolved bridge host this run actually used, matching opc_server above.

pid_constant_tags: Option<PidConstantTagsResponse>

Some exactly when routes::runs::require_writable_run’s tag-presence check would pass – i.e. when all three PID constant tags were configured on this run. The frontend uses this (together with driver/outcome/opc_server/bridge_host) to decide whether the post-hoc write/revert buttons are enabled and, when they are not, to explain why – without duplicating require_writable_run’s logic client-side or discovering ineligibility only after a failed request (api-post-run-write).

pid_parameter_labels: PidParameterLabelsResponse

Operator-facing calculated-result column labels from the run’s historical template snapshot. Empty user-template suffixes use the conventional P/I/D labels.

initial_readings: Option<InitialReadingsResponse>

timing_metrics: Option<TimingMetrics>

samples: Vec<SampleResponse>

results: Vec<ResultResponse>

writes: Vec<WriteResponse>

mv_actuations: Vec<MvActuationResponse>

restore_status: Option<RestoreStatus>

restore_detail: Option<String>

original_request: Option<StartRunRequest>

This run’s own request_json (db-run-request-snapshot), parsed back into a StartRunRequest, or None if it isn’t usable – see parse_stored_request. Powers the run detail page’s “Duplicate this run” action (ui-prefill-last-run): unlike GET /api/runs/last-request, which only ever answers for the single newest run, this lets the New tune form seed itself from this specific historical run regardless of how many later runs exist.

gateway_compatibility: Option<GatewayCompatibilityResponse>

Gateway protocol snapshot recorded before this run’s live mutation, when the run used OPC DA. None for simulator/replay runs and for OPC runs that predate the snapshot.

Trait Implementations

impl ComposeSchema for RunDetailResponse

fn compose(generics: Vec<RefOr<Schema>>) -> RefOr<Schema>

impl Debug for RunDetailResponse

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Serialize for RunDetailResponse

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl ToSchema for RunDetailResponse

fn name() -> Cow<'static, str>

Return name of the schema.

fn schemas(schemas: &mut Vec<(String, RefOr<Schema>)>)

Implement reference [utoipa::openapi::schema::Schema]s for this type.