Skip to main content

gameModelFlow

Diagnostics surface: stitch one flow correlation id into a single cross-engine timeline — the model events (gm event log), automation runs, and compute module runs that share the flowId minted at the entry edge (player gameModelInvoke / automation run / computeInvoke) and propagated across model_invoke, the event bus, and emit_compute_event. Each array is ordered by time ascending; an unknown flowId returns three empty arrays. Answers "what happened to this kill's reward" in one query instead of three hand-joined ones. Requires app-admin ('manage_apps').

gameModelFlow(
  appId: BigInt!
  flowId: String!
): GmFlowTimeline!

Arguments​

gameModelFlow.appId ● BigInt! non-null scalar​

The app (tenant) whose flow to stitch.

gameModelFlow.flowId ● String! non-null scalar​

The flow correlation id (UUID) — from the flowId field of a GmEvent, GmAutomationRun, or WasmModuleRun.

Type​

GmFlowTimeline object​

The stitched cross-engine timeline for one flow correlation id: every model event, automation run, and compute module run that shares the flow_id minted at the entry edge (player invoke / automation run / computeInvoke). Each array is ordered by time ascending, so the three together read as one causal diagnostics trace (e.g. mob kill -> compute event -> reward grant).