Fix elapsed runtime to start at execution launch (GEN-2119) - #175
Merged
exe-dev-github-integration[bot] merged 3 commits intoSep 18, 2026
Merged
Conversation
github-merge-queue
Bot
removed this pull request from the merge queue due to a conflict with the base branch
Sep 18, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to a conflict with the base branch
Sep 18, 2026
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
1 participant
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.
Run elapsed time now starts at successful execution launch, excluding the time spent waiting in the queue and preparing the launch.
Expose the existing, persisted job_runs.started_at through run list/detail responses and use it in both elapsed displays. Preserve created_at, show queue time separately on the run page, and avoid inventing runtime for runs without a start timestamp. The existing launch transaction already records the first start with COALESCE; no migration or queue-policy change is needed.
Validation: npm run build:css; npm run check (API boundaries, TypeScript, 152 tests, app and relay deployment dry runs); additional job-list browser regression passed (2 timing browser tests total); TypeScript recheck; git diff --check. Tests cover launch persistence, nullable query timestamps, queue-to-running transition, terminal runtime, and list timers.
Fixes GEN-2119
https://linear.app/generation/issue/GEN-2119/run-elapsed-time-is-incorrect