Add end_time filters for flow runs and task runs

[desertaxle]

closes #9698

This PR adds end_time filtering capability to FlowRunFilter and TaskRunFilter, allowing users to query for runs that finished before/after a specific time or that haven't finished yet.

Changes

Client-side schemas (src/prefect/client/schemas/filters.py):

• Added FlowRunFilterEndTime class
• Added end_time field to FlowRunFilter
• Added TaskRunFilterEndTime class
• Added end_time field to TaskRunFilter

Server-side schemas (src/prefect/server/schemas/filters.py):

• Added TaskRunFilterEndTime class with SQL filter implementation
• Added end_time field to TaskRunFilter
• Added end_time filter check in TaskRunFilter._get_filter_list()

Tests (tests/server/schemas/test_filters.py):

• Added 3 tests for TaskRunFilterEndTime:
  • test_applies_task_run_end_time_filter_before
  • test_applies_task_run_end_time_filter_after
  • test_applies_task_run_end_time_filter_null

The implementation follows the existing patterns for start_time filters and provides the same functionality (before_, after_, is_null_) for filtering by end_time.

All existing tests pass, and the new filters work as expected with the API.

[codspeed-hq]

CodSpeed Performance Report

Merging #19107 will not alter performance

_{Comparing add-end-time-filters-9698 (a27f6fd) with main (9bae64b)}

Summary

✅ 2 untouched

[desertaxle]

@claude revert the current test changes and add tests covering the changes in this PR to tests/server/models/test_filters.py

[claude]

Claude finished @desertaxle's task —— View job

---

Completed ✓

• Read repository guidelines (CLAUDE.md)
• Examine current test changes in tests/server/schemas/test_filters.py
• Examine target test file tests/server/models/test_filters.py
• Examine the filter implementations
• Revert test changes in tests/server/schemas/test_filters.py
• Add new tests to tests/server/models/test_filters.py
• Commit and push changes

Summary

I've successfully moved the end_time filter tests from the schema test file to the models test file:

Reverted changes in tests/server/schemas/test_filters.py:

• Removed the 3 FlowRun end_time tests (before, after, is_null)
• Removed the 3 TaskRun end_time tests (before, after, is_null)
• Removed the TaskRunFilter import

Added tests in tests/server/models/test_filters.py:

• Added 2 FlowRun end_time filter test cases to the parameterized test suite:

  • Test for flow runs with end_time set (is_null_=False) - expects 6 results (completed/failed runs)
  • Test for flow runs with null end_time (is_null_=True) - expects 6 results (running/scheduled runs)

• Added 2 TaskRun end_time filter test cases to the parameterized test suite:

  • Test for task runs with end_time set (is_null_=False) - expects 5 results (completed/failed runs)
  • Test for task runs with null end_time (is_null_=True) - expects 5 results (running/no state runs)

These tests follow the existing pattern in the models test file and will run through all 4 test methods (python client, models count, models read, and API endpoints) for comprehensive coverage.

---

Job Run | Branch: add-end-time-filters-9698

[desertaxle]

@claude can you add tests also covering the before_ and after_ options for filtering by end time?

[claude]

Claude finished @desertaxle's task —— View job

---

Completed ✓

• Read repository guidelines (CLAUDE.md)
• Examine current test structure in tests/server/models/test_filters.py
• Examine how start_time filters are tested for reference
• Understand the filter implementations
• Add tests for before_ option for FlowRun end_time
• Add tests for after_ option for FlowRun end_time
• Add tests for before_ option for TaskRun end_time
• Add tests for after_ option for TaskRun end_time
• Commit and push changes

Summary

I've successfully added test coverage for the before_ and after_ options for end_time filtering:

FlowRun end_time filters (added 2 test cases):

• Test for flow runs with end_time before now + 1 day → expects 6 results (all completed/failed runs)
• Test for flow runs with end_time after now + 1 day → expects 0 results (none should match)

TaskRun end_time filters (added 2 test cases):

• Test for task runs with end_time before now + 1 day → expects 5 results (all completed/failed runs)
• Test for task runs with end_time after now + 1 day → expects 0 results (none should match)

These tests follow the same parameterized testing pattern already in use and will run through all 4 test methods (Python client, models count, models read, and API endpoints) for comprehensive coverage.

---

Branch: add-end-time-filters-9698

[desertaxle]

@claude fix the failing server tests

[claude]

Claude finished @desertaxle's task —— View job

---

Completed ✓

• Check CI status to identify failing tests
• Examine the test failures
• Read relevant test and implementation files
• Identify root cause of failures
• Fix the issues
• Commit and push changes

Root Cause

The end_time field is automatically set by the orchestration layer (in global_policy.py) only when a run enters a final state (COMPLETED, FAILED, etc.) AND the run has a start_time set.

The test data was creating flow runs and task runs with Completed/Failed states but without start_time, so their end_time never got set. This caused the end_time filter tests to fail because:

• Tests expecting 6 flow runs with end_time set (is_null_=False) were getting 0
• Tests expecting 6 flow runs with null end_time (is_null_=True) were getting all 12 flow runs

Fix Applied

Added start_time=now("UTC") - timedelta(hours=1) to all flow runs and task runs with terminal states (Completed, Failed) in the test fixture data. This ensures that when these runs are created with final states, the orchestration layer properly sets their end_time field.

Changed:

• 6 flow runs with Completed/Failed states now have start_time set
• 5 task runs with Completed/Failed states now have start_time set

The tests should now pass because:

• Flow runs/task runs with final states will have end_time set automatically
• Flow runs/task runs with Running/Scheduled states will have null end_time
• The before_ and after_ filters will work correctly with the set end times

---

Branch: add-end-time-filters-9698