ReadonlycancelOnBackground: booleanThe app ends the flow when it goes to the background (cancelOnBackground).
Readonlymarker: numberThe QPL marker id (x-ig-salt-ids carries it as decimal text).
ReadonlystartedAtMs: numberWhen the app started it (the process clock, milliseconds).
Optional ReadonlytimeoutMs?: numberThe flow's own time-to-live: the app's logger ends it once this many milliseconds have passed since its start (e.g. 300 000 for the action flows started "if not ongoing"). Absent: no time-to-live of its own.
The app's QPL user-flow logger: starting until the process's launch has
finished its first flight of app-init requests, ready from then on. The
app's logger comes up asynchronously in the app-init graph
(QplXplatDelayedInitializer → the 03dR singleton, whose 03dR.A0B
gates the header) while the launch's first requests go out, so a request
the launch's first flight builds carries no x-ig-salt-ids whatever flows
run. It is the flow state's, not the process-start fact's: the logger
belongs to the flows it stamps, and a platform without one (iOS) carries
neither. A process the caller builds directly is one past its first flight
and starts ready; a launch sets starting itself (BeginUserFlowLoggingStartup) and closes it at the end of its first flight
(MarkUserFlowLoggingReady).
The mutable process holder of the running flows, in the order they started, and of the logger that renders them. The events change it in place, so a service value is never reassigned.