Session Logs

Use activity, logs, and execution traces to reconstruct what actually happened in the app.

Use when

• A workflow, channel, or board action behaved unexpectedly.
• You need evidence from logs instead of relying on chat memory.

Workflow

1. Identify the relevant session, workflow, task, or timestamp window.
2. Pull the smallest useful slice from logs, activity, executions, or metrics first.
3. Separate trigger, execution, side effects, and final user-visible output.
4. Highlight the first meaningful deviation, not every noisy line.
5. Tie the log evidence back to the product symptom and the likely fix area.

Deliverable

• Timeline of the key events.
• First failure or divergence point.
• Impacted component.
• Recommended next check or fix.