kestra-io/kestra

[Filters] Execution startDate/endDate clashes with timeRange

Open

#16,428 opened on Jun 1, 2026

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Java (26,854 stars) (2,579 forks)batch import
area/frontendgood first issue

Description

Describe the issue

Hitting the Executions' quick range filter when an absolute time range filter is active results in:

Illegal argument: Parameters 'startDate'/'endDate' and 'timeRange' are mutually exclusive

The precedence of both filters is not clear.

Reproduction steps

  1. Navigate to the Executions view
  2. Select the interval filter
  3. Set a custom range
  4. Hit the quick range filter (15m/1h/etc.)
  5. Request fails

Environment

  • Kestra Version: develop

Contributor guide

Tech stack
java
Domain
backendfrontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Examine the execution filter UI component and the backend API validation to understand the mutual exclusivity conflict between startDate/endDate and timeRange.