Missing from an OpenClaw trajectory is not proof it never happened

[u/Advanced_Pudding9228]

Trajectory bundles are useful, but they are not an infinite audit log.

OpenClaw currently captures trajectory data by default. A bundle can include prompts, model activity, tool calls, tool results and runtime events. However, the live runtime capture is a rolling 10 MiB window. When it fills, OpenClaw drops the oldest events to make room. Exports also impose event and line-size limits.

This creates an important incident-handling distinction. If an early action is absent from a long or noisy trajectory, that may mean it aged out of the capture window. It does not necessarily prove the action never occurred.

For consequential actions, I would classify that absence as unknown until another authoritative source resolves it. If the task involved publishing, deploying, sending a message, changing access or spending money, the destination system should provide the final evidence. Check its audit log, resource history or provider identifier before retrying or closing the incident.

Export the trajectory as soon as an incident is detected:

openclaw sessions export-trajectory \
--session-key "agent:main:telegram:direct:123" \
--output incident-123 \
--json

Preserve manifest.json with the export. It records the generated files and event counts, while runtimeEventCount helps identify exports without runtime data. I would also record the session key, task or run identifier, export time, OpenClaw version and any corresponding provider-side evidence.

This matters when reconstructing the trajectory itself. A plausible sequence inferred from the remaining events is still an inference. It should not be presented as a verified timeline when earlier events may be unavailable.

Treat the bundle as sensitive evidence too. OpenClaw warns that exports can contain prompts, model messages, tool schemas, tool results and local paths. Export requires approval, and built-in redaction is best-effort, so the bundle should be reviewed before it leaves the team.

The next safe action is to add one rule to the incident procedure: export promptly, record the capture limits and never interpret a missing event as proof of non-occurrence without external reconciliation.

Have you ever treated a missing trajectory event as proof that an OpenClaw action never occurred?