Cronstable
Cronstable is an in-container task scheduler for trusted administrators that creates, runs, suspends, deletes tasks, and views logs, history, resources, and schedule status in the Dashboard.
##Functional characteristics - Use `+ job` to create a new task in the Dashboard without editing YAML. You can fill in the name, Cron schedule, command, enable status, and execution timeout. - Tasks created within the application are saved in the server's private directory; they still exist after refreshing, exiting, reentering, and application restarting, and the same task list can be seen in different browsers. - Support the execution of common operations such as Run, Pause, Cancel, and Logs directly in the task list and details drawer, which is suitable for daily inspections and temporary intervention. - You can directly delete tasks managed within the application; for running tasks, you need to execute Cancel first, and then click Delete and Confirm delete continuously. - The Dashboard displays task status, Cron / `@reboot` schedule, last run, next run, success rate, and running trends. - Task details provide views such as Logs, History, Resources, Schedule, etc. - Support manual Run, Cancel, Pause and Resume; the suspended state can be retained across restarts after server state storage is enabled. - Supports keyword search, status filtering, sorting, next execution radar, activity heat map, scheduling pressure, weekly planning, Cron sandbox, and DAG observation. ###Daily usage 1. Use the search box, status button and sorting entry to locate the task first; when you need to see the overall load, switch to 'radar','heat','pressure' or 'week'. 2. If the current deployment has access control enabled for write operations, first click `token` in the upper right corner to save the Bearer Token. When a token is not saved,`Access token required` will pop up for server-side write operations such as create and delete. 3. Click the task line to open the details drawer and switch between Logs, History, Resources, and Schedule; only tasks with resource monitoring enabled will display process resource sampling. 4. Use Run when it needs to be executed immediately; Cancel when it needs to be terminated; Pause when it needs to be triggered by subsequent plans, and Resume when it needs to be restored. 5. When deleting a task, first confirm that there are no running instances, and then click Delete and Confirm delete.
