Customer story / 02:14 / Published 2025-05-16
On call with Codex
An on-call story moves through task history, an error trace, diagnostic logs, and a code diff while returning to the same developer.

Useful to borrow
Show the failure before the attempted fix and the inspectable change.
Do not infer
A code diff alone is not proof of service recovery or a passing test suite.
9 shot groups.
Read across from the observed content to its treatment and possible adaptation. Enlarge the frame for detail.
Approximate study intervals; horizontal scrolling reveals all columns on small screens.
| Moment / source | Reference frame | What is on screen | Framing / edit | Useful adaptation |
|---|---|---|---|---|
| Shot group 01 ≈ 00:00–00:22 Title / identityWatch from here ↗ | Sample 00:12.000 | On-call introduction Interview and workplace movement surround a triage title. | Human setting and chapter identity. | Establish the operational problem. |
| Shot group 02 ≈ 00:22–00:30 App / browser screenWatch from here ↗ | Sample 00:28.000 | Task history A list of coding tasks shows completed changes. | List detail crop. | Use history as context, not as proof of the new fix. |
| Shot group 03 ≈ 00:30–00:46 People / environmentWatch from here ↗ | Sample 00:40.000 | Interview context The developer speaks in several room framings. | Matched human coverage. | Explain the failure before entering logs. |
| Shot group 04 ≈ 00:46–00:58 App / browser screenWatch from here ↗ | Sample 00:52.000 | Error trace A monitoring view opens a trace and stack details. | Diagnostic interface in close-up. | Show the actual failure state. |
| Shot group 05 ≈ 00:58–01:18 App / browser screenWatch from here ↗ | Sample 01:08.000 | Task and logs A task request leads to shell logs and investigation text. | Input and evidence inserts. | Preserve errors and caveats instead of editing them away. |
| Shot group 06 ≈ 01:18–01:46 App / browser screenWatch from here ↗ | Sample 01:36.000 | Return to work Phone and laptop activity bridge to the development workspace. | Physical device coverage. | Keep the human context tied to the same task. |
| Shot group 07 ≈ 01:46–02:00 App / browser screenWatch from here ↗ | Sample 01:48.000 | Diff and follow-up A code diff and a contextual Code action appear. | Whole change then targeted control. | Show the inspectable change; verify the outcome separately. |
| Shot group 08 ≈ 02:00–02:12 People / environmentWatch from here ↗ | Sample 02:08.000 | Closing interview The developer returns to the original interview framing. | Human conclusion. | Separate the story's ending from technical verification. |
| Shot group 09 ≈ 02:12–02:14 Title / identityWatch from here ↗ | Sample 02:12.000 | End identity A mark forms on white. | Minimal outro. | Use a recognizable close. |