# Session-replay investigation

Guide: https://yenra.com/bea-tealeaf/
Use sanitized identifiers and synthetic test values. Store this record in an access-controlled location appropriate to your incident. Do not paste passwords, raw personal details or payment data.

## Scope
- Symptom and expected behavior:
- Application release, browser and capture SDK/version:
- Sanitized session/request IDs:
- Timezone and clock source; known offset or uncertainty:

## Timeline
For each event record: timestamp, observation, evidence source, request ID, uncertainty and next check.

## Investigation
- Replay observation:
- Browser request/exception evidence:
- Server response/trace:
- Business operation committed? Evidence:
- Hypothesis and alternatives:
- Test fixture and expected outcome:
- Actual result before/after fix:
- Remaining uncertainty, owner and follow-up date:

## Capture verification before release
- Input values, rendered text, URLs, errors and dynamic content reviewed:
- Synthetic values used:
- Outgoing capture and replay inspected:
- Masking/omission result:
- Access and retention reviewed:

Fictional example: request R-42 returns success, a missing-field exception follows, and the UI spinner remains. A test response reproduces the fault. Verify transaction state separately before recommending a retry.