WEBVTT 00:00:00.030 --> 00:00:03.205 position:50% align:center size:88% Let’s review the platform incident-response procedure. 00:00:03.280 --> 00:00:07.411 position:50% align:center size:88% This is a procedural walkthrough, not a failure or recovery drill. 00:00:07.891 --> 00:00:12.316 position:50% align:center size:88% Start by preserving the onset, scope and most recent deployment. 00:00:12.391 --> 00:00:16.116 position:50% align:center size:88% The saved rehearsal health response names the observed build. 00:00:16.191 --> 00:00:19.191 position:50% align:center size:88% Its timestamp belongs to this observation. 00:00:19.266 --> 00:00:22.916 position:50% align:center size:88% A successful health check does not prove every path is healthy. 00:00:22.991 --> 00:00:27.603 position:50% align:center size:88% The chapter is a published runbook, not a newly deployed application page. 00:00:29.480 --> 00:00:32.530 position:50% align:center size:88% The runner panel reports job claims and leases. 00:00:32.605 --> 00:00:34.705 position:50% align:center size:88% It does not prove pod readiness. 00:00:34.780 --> 00:00:38.655 position:50% align:center size:88% For a Pending runner, ask the platform team to check capacity. 00:00:38.730 --> 00:00:42.330 position:50% align:center size:88% For a silent runner, check its heartbeat and deployment state. 00:00:42.405 --> 00:00:46.180 position:50% align:center size:88% The runbook gives a three-minute lease and at most three attempts. 00:00:46.280 --> 00:00:50.067 position:50% align:center size:88% Those are recovery rules, not a measured repair in this recording. 00:00:51.920 --> 00:00:55.345 position:50% align:center size:88% Check pool use against the whole database connection limit. 00:00:55.445 --> 00:00:57.920 position:50% align:center size:88% More pools can make exhaustion worse. 00:00:57.995 --> 00:01:01.395 position:50% align:center size:88% Also inspect scheduler leadership and audit sealing. 00:01:01.470 --> 00:01:04.645 position:50% align:center size:88% The monitoring rules name the evidence to request. 00:01:04.745 --> 00:01:08.411 position:50% align:center size:88% This review contains no new monitoring or database measurement. 00:01:10.360 --> 00:01:13.885 position:50% align:center size:88% Read the recorded licence state separately from transport errors. 00:01:13.985 --> 00:01:18.135 position:50% align:center size:88% DNS and TLS belong with the cloud or DNS team. 00:01:18.235 --> 00:01:21.885 position:50% align:center size:88% Gateway errors need the gateway owner and the configured model. 00:01:21.960 --> 00:01:25.135 position:50% align:center size:88% A budget block needs the workspace owner’s decision. 00:01:25.210 --> 00:01:29.210 position:50% align:center size:88% For a failed release, preserve the image, chart and key pairing. 00:01:29.310 --> 00:01:32.269 position:50% align:center size:88% Use the approved rollback procedure with the current keys. 00:01:34.400 --> 00:01:38.250 position:50% align:center size:88% Pause all agents and Stop this run are operational actions. 00:01:38.300 --> 00:01:41.750 position:50% align:center size:88% The owner chooses the scope; this walkthrough presses neither. 00:01:41.825 --> 00:01:45.925 position:50% align:center size:88% Pause keeps intake open, while blocked starts need human handling. 00:01:46.025 --> 00:01:49.250 position:50% align:center size:88% Stopping a run requests cancellation at a checkpoint. 00:01:49.325 --> 00:01:53.075 position:50% align:center size:88% Confirm its terminal result instead of assuming the click finished it. 00:01:53.150 --> 00:01:56.075 position:50% align:center size:88% Discovery has its own Cancel action. 00:01:56.150 --> 00:01:59.552 position:50% align:center size:88% Do not delete durable database rows to clear a queue. 00:02:01.560 --> 00:02:06.010 position:50% align:center size:88% Send a sanitized record of time, scope, build and actions taken. 00:02:06.110 --> 00:02:09.010 position:50% align:center size:88% Use the agreed contacts and response arrangement. 00:02:09.085 --> 00:02:11.885 position:50% align:center size:88% A Ready pod alone does not close an incident. 00:02:11.960 --> 00:02:16.260 position:50% align:center size:88% Check affected paths, intake errors, queued work and audit sealing. 00:02:16.360 --> 00:02:20.235 position:50% align:center size:88% Record the cause, corrective action and prevention owner. 00:02:20.310 --> 00:02:24.387 position:50% align:center size:88% This procedure has not demonstrated a repair or measured recovery.