The Scheduler tab only supports create / toggle / delete. Changing a command, its workers or its interval means deleting and recreating it (losing last_run history). There is no Run now action to test a schedule, and although the backend supports schedule_type: 'cron' (calculateNextRun via cron-parser) the create modal only offers interval/hourly/daily.
Additional gaps: daily times are interpreted in server local time with no timezone hint; the "in Xm" countdown only updates on refresh; there is no link from a schedule to its past executions even though GET /api/executions?started_by=scheduler:<name> would provide it.
Suggested fix
PUT /api/scheduled-commands/:id + edit modal.
POST /api/scheduled-commands/:id/run and a Run Now button.
Cron option with a live "next 3 runs" preview; show timezone.
"View runs" button that opens the Executions tab pre-filtered.
## Overview
The Scheduler tab only supports create / toggle / delete. Changing a command, its workers or its interval means deleting and recreating it (losing `last_run` history). There is no **Run now** action to test a schedule, and although the backend supports `schedule_type: 'cron'` (`calculateNextRun` via cron-parser) the create modal only offers interval/hourly/daily.
Additional gaps: daily times are interpreted in server local time with no timezone hint; the "in Xm" countdown only updates on refresh; there is no link from a schedule to its past executions even though `GET /api/executions?started_by=scheduler:<name>` would provide it.
## Suggested fix
- `PUT /api/scheduled-commands/:id` + edit modal.
- `POST /api/scheduled-commands/:id/run` and a Run Now button.
- Cron option with a live "next 3 runs" preview; show timezone.
- "View runs" button that opens the Executions tab pre-filtered.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Overview
The Scheduler tab only supports create / toggle / delete. Changing a command, its workers or its interval means deleting and recreating it (losing
last_runhistory). There is no Run now action to test a schedule, and although the backend supportsschedule_type: 'cron'(calculateNextRunvia cron-parser) the create modal only offers interval/hourly/daily.Additional gaps: daily times are interpreted in server local time with no timezone hint; the "in Xm" countdown only updates on refresh; there is no link from a schedule to its past executions even though
GET /api/executions?started_by=scheduler:<name>would provide it.Suggested fix
PUT /api/scheduled-commands/:id+ edit modal.POST /api/scheduled-commands/:id/runand a Run Now button.