Development record
Re-running a failed attribution run after fixing the pull-request body (gh run rerun on the old run) replays the event the run was started with, so it checks the old body again and fails. The re-run joins the attribution-<pr> concurrency group and cancels the newer run that the body edit started, which would have passed. On 2026-10-26, PRs #1129 and #1133 each sat red for about four hours: the edited runs 40325771175 and 40325732363 were cancelled, and runs 40298736534 and 40298846131 failed again on the bodies they started with.
issueresolvedminoriss-2610261339023831
Re-running a failed attribution run after fixing the pull-request body (gh run rerun on the old run) replays the event the run was started with, so it checks the old body again and fails. The re-run joins the attribution-<pr> concurrency group and cancels the newer run that the body edit started, which would have passed. On 2026-10-26, PRs #1129 and #1133 each sat red for about four hours: the edited runs 40325771175 and 40325732363 were cancelled, and runs 40298736534 and 40298846131 failed again on the bodies they started with.
Frontmatter
| id | iss-2610261339023831 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610261339023831-re-running-a-failed-attribution-run.md
open on GitHub ↗ · commit history ↗