feat: emit created_at on workflow_run_jobs - #1
Merged
malhussan merged 1 commit intoAug 13, 2026
Conversation
malhussan
force-pushed
the
feature/workflow-job-created-at
branch
from
August 13, 2026 09:04
d54e5cf to
bf7487a
Compare
The API returns created_at on every job, but the stream schema does not declare it, so the SDK drops it before it reaches the target. created_at is the time the job was queued. started_at is the time a runner picked it up.
JohannesRudolph
approved these changes
Aug 13, 2026
JohannesRudolph
left a comment
Member
There was a problem hiding this comment.
lgtm. probably the easiest way to get this in. I wonder however if we should also update the tap to its remote upstream - surely a lot has changed. OTOH - if it works it works, no point in rocking the boat
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.
The GitHub API returns
created_aton every workflow job, but the stream schema does not declare it, so the SDK drops it before it reaches the target.This adds the property. Nothing else changes.
created_atis the time the job was queued.started_atis the time a runner picked it up.Checked against one job, where the API returned
created_atat 06:53:03 andstarted_atat 06:56:24.Two notes:
feature/fix-actions-streamsrather thanmain, because that branch carries the three workflow-stream fixes that are not onmain: incremental loading forworkflow_runs, the lookback window, and dropping state partitions forworkflow_run_jobs. Basing this onmainwould mean losing those three when the pin moves.created_at. Only new syncs carry it, so a full re-sync is needed for history.