The current scheduler task run table is growing without bounds. This will cause problems sooner rather than later, so we should make sure we can keep it manageable and queryable.
We're also adding one-shot tasks to the scheduler, and it doesn't make sense to keep those around forever and bloat the live database once they've been completed.
We're now using elasticsearch for long-term structured logging. It would make sense to archive old tasks over there as well.