Skip to content

fix: block stuck on "running" (and a dead Stop button) when another block interrupts it #1573

fix: block stuck on "running" (and a dead Stop button) when another block interrupts it

fix: block stuck on "running" (and a dead Stop button) when another block interrupts it #1573

Triggered via pull request August 21, 2026 09:57
Status Success
Total duration 2m 44s
Artifacts

test.yml

on: pull_request
Lint & Typecheck
29s
Lint & Typecheck
Unit Tests
58s
Unit Tests
Build Verification
28s
Build Verification
E2E Tests
2m 34s
E2E Tests
Runbook Tests
49s
Runbook Tests
Runbook Tests (GitHub App Token)
12s
Runbook Tests (GitHub App Token)
Documentation Tests
32s
Documentation Tests
CI Summary
3s
CI Summary
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
eslint(no-unused-vars): testdata/sample-runbooks/lambda/templates/lambda-src/nodejs/index.mjs#L35
Catch parameter 'e' is caught but never used.
eslint(no-unused-vars): testdata/sample-runbooks/lambda/templates/lambda-src/nodejs/index.mjs#L28
Variable 'queryParams' is declared but never used. Unused variables should start with a '_'.
eslint(no-unused-vars): testdata/sample-runbooks/lambda/templates/lambda-src/nodejs/index.mjs#L27
Variable 'path' is declared but never used. Unused variables should start with a '_'.
eslint(no-unused-vars): testdata/sample-runbooks/lambda/templates/lambda-src/nodejs/index.mjs#L26
Variable 'httpMethod' is declared but never used. Unused variables should start with a '_'.
eslint(no-empty-pattern): web/e2e/fixtures.ts#L53
Empty object binding pattern