Feature Area
/area frontend
What feature would you like to see?
I would like to see start_time and end_time displayed directly in the recurring runs table.
Currently, the recurring runs list shows whether a job is enabled or disabled, but it is not immediately clear whether an enabled recurring run is still effectively active if an end_time was configured.
A possible improvement could be to add columns such as:
- Start time
- End time
- Schedule status / Effective status
The schedule status could be derived from the current time and the configured schedule window, for example:
Scheduled — enabled, but start_time is in the futureActive — enabled and current time is within the schedule windowExpired — enabled, but end_time is set and already passedDisabled — manually disabled
Alternatively, even just displaying start_time and end_time in the table would already improve the user experience, because users would not need to open each recurring run individually to understand its actual schedule window.
What is the use case or pain point?
When managing multiple recurring runs, it is hard to quickly understand which ones are still expected to trigger new runs and which ones have already passed their configured end_time.
For example, a recurring run can still be shown as Enabled even after its end_time has passed. From a scheduler perspective this may be correct, because enabled/disabled is a separate mode from the schedule window. However, from a user and operations perspective this can be confusing.
Users may see an enabled recurring run and assume it is still active, even though it will no longer create new runs because the configured end_time is already in the past.
Showing the start and end time directly in the recurring runs table, or adding a derived schedule status, would make it much easier to:
- distinguish active recurring runs from expired ones;
- review temporary recurring runs;
- clean up old recurring jobs;
- avoid confusion during operational checks;
- understand the effective lifecycle of a recurring run without opening each job details page.
Is there a workaround currently?
Currently, the workaround is to open each recurring run details page or inspect the recurring run through the API/SDK and manually check its start_time and end_time.
This works, but it is inconvenient when there are many recurring runs. It also makes it easy to miss expired recurring runs that still appear as Enabled in the list.
Adding these fields directly to the recurring runs table, or showing a derived schedule status, would make this information available at a glance.
Love this idea? Give it a 👍.
Feature Area
/area frontend
What feature would you like to see?
I would like to see
start_timeandend_timedisplayed directly in the recurring runs table.Currently, the recurring runs list shows whether a job is enabled or disabled, but it is not immediately clear whether an enabled recurring run is still effectively active if an
end_timewas configured.A possible improvement could be to add columns such as:
The schedule status could be derived from the current time and the configured schedule window, for example:
Scheduled— enabled, butstart_timeis in the futureActive— enabled and current time is within the schedule windowExpired— enabled, butend_timeis set and already passedDisabled— manually disabledAlternatively, even just displaying
start_timeandend_timein the table would already improve the user experience, because users would not need to open each recurring run individually to understand its actual schedule window.What is the use case or pain point?
When managing multiple recurring runs, it is hard to quickly understand which ones are still expected to trigger new runs and which ones have already passed their configured
end_time.For example, a recurring run can still be shown as
Enabledeven after itsend_timehas passed. From a scheduler perspective this may be correct, because enabled/disabled is a separate mode from the schedule window. However, from a user and operations perspective this can be confusing.Users may see an enabled recurring run and assume it is still active, even though it will no longer create new runs because the configured
end_timeis already in the past.Showing the start and end time directly in the recurring runs table, or adding a derived schedule status, would make it much easier to:
Is there a workaround currently?
Currently, the workaround is to open each recurring run details page or inspect the recurring run through the API/SDK and manually check its
start_timeandend_time.This works, but it is inconvenient when there are many recurring runs. It also makes it easy to miss expired recurring runs that still appear as
Enabledin the list.Adding these fields directly to the recurring runs table, or showing a derived schedule status, would make this information available at a glance.
Love this idea? Give it a 👍.