[Improvements]: Scheduled tasks

[andrasbacsai]

Scheduled tasks added here, but there are a few improvements that will be added:

• [ ] Add email notifications for success/fail
• [ ] Trim executions to last ~20 or so to limit db growth for historic runs
• [ ] Execution time limits
• [ ] Display next run time, total execution time
• [ ] Probably some standardisation/consistency issues in here

[gausie]

I'd also love to be able to control the Scheduled Tasks as IAC by having a .crontab or similar file in the project's codebase. Is this a useful feature to track here or should it be considered separately?

[peaklabs-dev]

• [ ] Also consider adding Slack notifications for failed tasks.
• [ ] Add tasks globally to coolify so for the coolify instance there can be cron jobs and for each container individually
• [ ] The pop-up input is too small for long cron task, consider using a wider area on the dashboard.
• [ ] Add a Timzone setting so we can select the timezone for each cron -> so it runs when we expect it

[gausie]

A task of mine seems to have got stuck a few days ago and there's no way to cancel it, nor did the task re-attempt the next day. Could we supply a timeout or something?

[aspantel]

We don't see the output of our scheduled tasks in our log drains. Is this not available? Any ETA for this?

We use scheduled tasks as health checks and getting their output is essential!

[jonnyscholes]

My "Recent executions" seem to change order on page load. This sometimes means the most recently executed task (even if it's currently running) don't show up in the list. Does this sound right?

Would you be open to a PR that ensures the recent executions are the 20 most recent ones?

[martmalo]

Also want to mention that failed cron jobs shows logs once I click on them, but successful ones does not. is this meant to be like that?

Edit: Did not notice that someone mentioned this already.

[benjamin-steurer]

Is there any plan to integrate this with the log drains?

[HashimTheArab]

Is it possible to cancel stuck tasks?