WEBVTT

1
00:00:00.250 --> 00:00:01.920
How an open ask lives.

2
00:00:01.920 --> 00:00:05.500
An ask is state, projected from the load's log.

3
00:00:06.100 --> 00:00:07.560
7:01 AM.

4
00:00:07.560 --> 00:00:14.330
The SOP opens an ask: a target, attempts, a timer and a pinned SOP version.

5
00:00:14.930 --> 00:00:16.460
7:13 AM.

6
00:00:16.460 --> 00:00:19.530
An unrelated question gets its answer.

7
00:00:19.530 --> 00:00:21.300
The ask does not move.

8
00:00:21.900 --> 00:00:23.440
7:31 AM.

9
00:00:23.440 --> 00:00:28.930
The timer is current and the ask still open: the SOP takes the next step.

10
00:00:29.530 --> 00:00:30.900
8:01 AM.

11
00:00:30.900 --> 00:00:32.600
Attempts are used up.

12
00:00:32.600 --> 00:00:35.980
The escalation chain runs in one decision.

13
00:00:36.580 --> 00:00:37.870
7:20 AM.

14
00:00:37.870 --> 00:00:41.280
Another run: the dispatcher emails the ETA.

15
00:00:41.280 --> 00:00:44.390
The ask is resolved, its timer cancelled.

16
00:00:44.990 --> 00:00:46.720
7:25 AM.

17
00:00:46.720 --> 00:00:49.010
The old timer arrives anyway.

18
00:00:49.010 --> 00:00:52.150
The ask is closed: noop, no model call.

19
00:00:52.750 --> 00:00:54.400
7:31 AM.

20
00:00:54.400 --> 00:00:56.910
The same timer, delivered twice.

21
00:00:56.910 --> 00:01:00.430
Its event id is already in the log: dropped.

22
00:01:01.030 --> 00:01:03.190
State decides, not the timer.

23
00:01:03.190 --> 00:01:07.510
Stale or duplicated timers are noops, with no model call.