Ververica Platform scenario diagnostics
get_scenario_diagnostics supports VVP per-job and session targets. Read the returned job IDs, engine states,
observed restart counts, start/end times and available root exceptions, failure messages and GENERAL_FAILURE events. Use the returned job ID
for subsequent diagnostics. historyStatus=partial means partial VVP evidence, not complete Flink exception history.
Failure evidence uses a 31 KiB budget. A failure timestamp of zero is unknown. droppedFailures and stackTraceTruncated indicate bounded evidence.
A successful Designer DEPLOY records submission. A worker can subsequently fail during graph compilation or service initialization. Do not exclude compilation failure because submission succeeded. An unavailable adapter, empty root exception or empty history does not prove a job was healthy or absent. Separate facts, gaps and hypotheses.
The scenario log's exception groups are an independent source; see the deployment-diagnostics skill. Upgrading
Designer does not replace Nu jars baked into a VVP with-dependencies runtime image; that image must also contain the
error-reporting code, and the scenario must use it after redeployment. Only the current job carries the Nussknacker deployment ID; older jobs carry
none.