Repository navigation
fix(workflows): use larger argo page size for client-side filtering - #1712
Merged
Merged
Conversation
davehadley
requested changes
Oct 8, 2026
hazdl
force-pushed
the
hz/para-filter-limit
branch
from
October 8, 2026 13:05
4c8449d to
fa52351
Compare
Contributor
Author
|
Fixed it. I removed the spurious files. When I last added |
davehadley
approved these changes
Oct 8, 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
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.
Analysis Platform - AP-1366
Fixes inefficient workflow filtering when filtering by parameters or annotations.
Previously, the GraphQL limit was also used as the Argo API page size. This meant that a small GraphQL limit, such as limit: 10, could cause many Argo API requests when searching through a large number of workflows with few or no matches.
The client-side filtering path now uses a separate Argo page size of 1000 workflows per request.
The GraphQL limit remains unchanged and continues to control the maximum number of matching workflows returned to the user.
Changes
Testing