A trigger that acts as a kind of “scheduled cache,” executing only with the data received according to the schedule provided by other flows. Alternatively, a kind of block within a flow, similar to Async. Something like a “Scheduled folder.”
This is because current solutions, such as storing in a database and using a minute-by-minute trigger, is not that precise.
More options for scheduled tasks are planned. Ideally, the ability to schedule a task to happen at an exact date/time arbitrarily in the future, and maybe some kind of page listing scheduled tasks with the option to dismiss them.
This will probably come alongside the revamp of async folders (which will enable this). Precise day/time control (think alarm app UI, where you can pick a specific time and day(s) of week) will also be coming in a new cron trigger eventually.
There’s some runtime concerns for this so it’ll likely be limited to a specific number of scheduled tasks per bot, and there will likely be limits on how far in the future things can be scheduled (since we don’t want to be storing potentially very large flow state for many months or years).