Repository navigation
Show recent executions when filtering by start time - #942
Merged
Sovietaced merged 1 commit intoOct 25, 2026
Merged
Sovietaced merged 1 commit into
Sovietaced merged 1 commit into
Conversation
Sovietaced
force-pushed
the
1fanwang/start-time-filter-execution-created-at
branch
from
October 10, 2026 17:50
7d7b001 to
46083d2
Compare
Signed-off-by: 1fanwang <1fannnw@gmail.com>
Sovietaced
force-pushed
the
1fanwang/start-time-filter-execution-created-at
branch
from
October 16, 2026 23:48
46083d2 to
2a382f7
Compare
Sovietaced
approved these changes
Oct 16, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #942 +/- ##
=======================================
Coverage 55.56% 55.56%
=======================================
Files 588 588
Lines 15444 15444
Branches 2835 2835
=======================================
Hits 8582 8582
Misses 6862 6862 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
TL;DR
Recent executions can disappear when the Start Time filter is active, because the UI filters and sorts on the row timestamp instead of the execution timestamp.
This change switches workflow execution queries to execution_created_at and node execution filters to node_execution_created_at, so the filter matches the timestamp Flyte records for the execution itself.
Type
Are all requirements met?
Complete description
The Start Time filter was building created_at predicates, and the execution list default sort also used created_at. In Flyte admin, created_at is the database row timestamp, while execution_created_at and node_execution_created_at track the execution closure timestamp users see as the run start time. If those timestamps drift, the Last Hour and Last 24 hours filters can hide runs that started recently.
This patch points workflow execution sorting and filtering at execution_created_at and points node execution filtering at node_execution_created_at.
Tracking Issue
N/A
Follow-up issue
N/A
Testing Done
Seed a real execution, then backdate only the database row timestamp so created_at and execution_created_at diverge.
Reproducer source: simple_wf.py