Repository navigation
fix(runner): clean up completed Application pool runners - #148
Merged
Merged
Conversation
lweberru
requested review from
Breeless,
JoshSTACKIT,
LembDo and
dweezl
as code owners
October 23, 2026 14:38
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Completed Application jobs left consumed one-shot CF web processes running. Ten retained runners filled the Dev organization memory quota and prevented the next Runner template from staging, despite standby capacity being set to one.
Pool maintenance now retires Application leases only after a durable succeeded/failed dispatch with the same job, app and source droplet. The existing scoped CF deletion path handles those leases and retries failures. Running jobs and reconciliation cases remain untouched; state and saved plan artifacts are retained. Migration 067 adds a narrowly scoped function without exposing tenant job records. English and German operating guidance explains cleanup and staging headroom.
Validation: complete Configurator check (1056 passed, 71 gated skips); real PostgreSQL identity and pool regressions, including active jobs, mismatched scope/app/droplet, completion and idempotency. Final database run: 66 passed, including the unresolved-job regression. Final focused pool run: 12 passed, including deletion failure/retry; platform database suite: 63 passed. Final typecheck and lint pass.
Refs #147. Historical Dev cleanup and a successful release remain required before closing that issue. No customer Plan/Apply or State unlock is included.
CI attempt 1 exceeded the existing 15-minute job budget after OS browser dependencies took 8m11s to download. All preceding checks passed; UI execution was incomplete. Only that failed job is rerun on the unchanged commit with the complete suite and unchanged limits.