Event and task runs may be scheduled to perform in the future. They will not have any effect until they are performed. This means that their eventual performance may be impacted by changes to a store's Mechanic account, prior to the scheduled performance time.
Event runs may be scheduled using the Event action, using its
run_at option to define the time at which the run should be performed.
The task runs that arise from a scheduled event run will not be established until the event run is performed. (This does not apply if the
task_ids option is used, which determines ahead of time which tasks may be run in response to the new event.) This means that changes to the set of enabled tasks can have an impact on what tasks are actually run, in response to a scheduled event run.
Task runs may be scheduled using subscription offsets, in which a task states that it wishes to run later (by some amount of time) than the event that triggers it.
Subscription offsets only allow for relative scheduling (e.g. "run 5 days after event x"); by contrast, absolute scheduling (e.g. "run on December 16th at 2:30pm") can be indirectly achieved using the Event action, scheduling an event run which may then give rise to a task run at the scheduled time.
If a task is disabled or deleted at the time a task run comes due, the task run will still perform at the scheduled time, but will fail instantly.