BugFix: Use recentFlowRunFilter instead of flowRunFilter #8380
Conversation
This file contains 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
✅ Deploy Preview for prefect-orion ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
@marichka-offen - need your 👀 here! I'm not certain if the difference was deliberate but it feels confusing to see more runs on the queue page than its parent pool page. |
3 tasks
zanieb
pushed a commit
that referenced
this pull request
Feb 3, 2023
zanieb
pushed a commit
that referenced
this pull request
Feb 3, 2023
serinamarie
pushed a commit
that referenced
this pull request
Feb 6, 2023
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.
Uses the recentFlowRunFilter instead of runFilter to match the date filter that's applied on work pools and the empty state message.
Example
Checklist
<link to issue>"fix,feature,enhancement