Skip to content
TheChatArchiveThe Chat Archive
x-ai/grok-4.5· unknownHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

ISSUE DESCRIPTION [Filters] Backend do not accept conditional groups Describe the issue…

  1. User

    ISSUE DESCRIPTION

    [Filters] Backend do not accept conditional groups

    Describe the issue

    HTTP 400 is returned at a simple conditional group filter query.

    Reproduction

    1. Navigate to the Executions view
    2. Add a new conditional group to the default set of filters
    3. Keep the OR operator
    4. Add a new filer - e.g. labels foo:bar
    5. HTTP 400 response with:

    Invalid query filters: Provided query filters are invalid: Field TIME_RANGE is not supported for resource EXECUTION. Supported fields are QUERY, SCOPE, FLOW_ID, START_DATE, END_DATE, STATE, LABELS, TRIGGER_EXECUTION_ID, CHILD_FILTER, NAMESPACE, KIND, PARENT_ID

    Environment

    • Kestra Version: develop

    Interface

    No new interfaces are introduced.

    ADDITIONAL ADVICE

    Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use git checkout <file> to restore the file to its original state. You can also reset all changes in the repository using git reset --hard command. Additionally, you can use git stash and git stash pop to temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you call submit) using git status or git diff commands. However you don't need to use git add or git commit before submitting your changes. In fact, submit only submits currently unstaged changes because it uses git diff to get the changes that need to be submitted.

    CHECKLIST

    Before submitting your solution, please go over the following checklist and make sure you've done everything:

    • If an error was reported in the issue description, I have successfully reproduced it.
    • If an error was reported in the issue description, I have confirmed that my fix resolves the error.
    • I have thought about edge cases and made sure my fix handles them as well.
    • I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.

    Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!

    (Current directory: /kestra, current file: none) bash-$

  2. Assistant

    I'll start by exploring the repository structure and searching for code related to query filters and conditional groups.

  3. Assistant

    Let me search for the error message and filter-related code more specifically.

  4. Assistant

    Searching more broadly for filter validation and related terms.

  5. Assistant

    Strange, no results. Maybe the code is generated or the error is constructed differently. Let me check git log and AGENTS.md

  6. Assistant

    Strange that TIME_RANGE had no matches. Let me try differently - maybe case sensitivity or path issues.

  7. Assistant

    That's weird - rg isn't finding things. Maybe there's something wrong with the path or files are nested differently.

  8. Assistant

    Found the key files. Opening QueryFilter and related validation utilities.

  9. Assistant

    Let me continue reading QueryFilter and QueryFilterUtils, and look at how filters are validated.

  10. Assistant

    Inspecting Resource validation and how filters get transformed.

  11. Assistant

    Reading the validation logic and EXECUTION resource field definitions.

  12. Assistant

    Ah, EXECUTION doesn't include TIME_RANGE. So TIME_RANGE is typically converted to START_DATE before validation. Let me see how validation is called and the convert flow.

  13. Assistant

    The bug is likely that TIME_RANGE conversion doesn't recurse into conditional group children. Checking the binder and execution controller flow.

  14. Assistant

    Searching for where validateQueryFilters is invoked and reviewing the annotation.

  15. Assistant

    Validation happens in AbstractJdbcRepository. And replaceTimeRange is called after binding, before the repository. Let me look at the flow more carefully: The issue is that replaceTimeRange is not being called for conditional groups, so TIME_RANGE remains in the filter tree and validation fails.

    I need to trace exactly where replaceTimeRangeWithComputedDateFilter is invoked and why it doesn't reach conditional groups.

  16. Assistant

    Checking how the UI encodes conditional group filters and what happens around TIME_RANGE handling.

  17. Assistant

    Let me look at how filters are encoded for API, especially with OR groups.

  18. Assistant

    There's ui/src/utils/filters.ts

  19. Assistant

    Root cause found: with conditional groups, TIME_RANGE is nested under OR and not rewritten. Checking related helpers, then implementing a recursive fix.

  20. Assistant

    Checking DateUtils timeline validation and recent related commits for context.

  21. Assistant

    Implementing recursive TIME_RANGE replacement and timeline extraction so nested conditional groups work.

  22. Assistant

    Let me update TimeLineSearch and QueryFilterUtils and DateUtils.

  23. Assistant

    Now updating QueryFilterUtils to recurse into nested filter groups.

  24. Assistant

    I'll rewrite the update methods to recurse into nodes.

  25. Assistant

    Updating DateUtils.validateTimeline to handle nested filter groups as well.

  26. Assistant

    Updating DateUtils to recurse into nested groups for timeline validation.

  27. Assistant

    Verifying the full QueryFilterUtils file and writing a reproduction script.

  28. Assistant

    Running unit tests for the affected classes to verify the fix.

  29. Assistant

    The output got truncated - need to see if tests passed.

  30. Assistant

    Tests are UP-TO-DATE which is suspicious — forcing a clean rebuild of the changed modules.

  31. Assistant

    Compilation succeeded. Now forcing the tests to re-run.

  32. Assistant

    Creating a temporary test to reproduce the nested conditional-group case and confirm the fix.

  33. Assistant

    Using the edit tool to add a temporary nested-group test.

  34. Assistant

    I'll add a temporary test then remove it after verification.

  35. Assistant

    Also verify OLD code would have failed - we believe it would. Run the nested test.

  36. Assistant

    Confirming the nested case fails without the fix, then restoring it.

  37. Assistant

    Confirmed the regression. Restoring the fixedand removing the temporary test.

  38. Assistant

    Re-running existing tests to confirm the restored fix still passes.

  39. Assistant

    All tests passed. Reviewing the final diff, then submitting.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.