With one (or more) actions selected in the actions window:
- Choose ➤ to suspend an action's schedule.
- Choose ➤ to reactive a previously suspended schedule.
For actions in a sidebar:
- Choose or
from the action (
) button
Actions can be scheduled to run automatically, automating tasks like the capture of items and archive maintenance.
Note: the capture assistant will create a set of scheduled actions for you. If you are new to action schedules, you might want to start by using the capture assistant and then review the actions it creates to see how they have been scheduled.
Actions can be scheduled to run at a particular time (see Time Schedules) or run in response to an event (see Event Schedules).
Actions are run in the order they are scheduled.
Multiple actions that use the same archive (or resource) are queued and run sequentially. To run a sequence of actions in a particular order, stagger their run times by one minute (or more)—capture at 2:00, merge at 2:01, compact at 2:02, for example. The merge action won't start until the capture action has finished.
Also see scheduler preferences.
You can temporarily suspend the schedule of a specific action. Once suspended, the action won't run automatically until its schedule is resumed.
With one (or more) actions selected in the actions window:
For actions in a sidebar:
) buttonYou can also place a hold on all schedules for a period of time. When the hold period expires, all actions that were scheduled to run during that time are started.
Holding all schedules is useful when you don't want QRecall running actions while you need all of your system resources or you are making big changes (upgrading your operating system, partitioning new drives, moving archives, editing a bunch of actions, and so on).
To hold all scheduled actions:
To recend the hold and immediately resume all schedules:
You can also hold the schedule using the Activity Monitor's control menu or from the command line.
There's a subtle difference between suspending a schedule and holding them. While a schedule is suspended, it is not active. A schedule that is held is still active, but won't start until the hold period elapses.
As an example, let's say an action is scheduled to run at 1:30 every day. If the schedule is suspended at 1:00 and resumed again at 6:00, the action will not run (until tomorrow), because it was suspended at the time it would have normally ran.
If, however, at 1:00 all schedules are held until 6:00, the action will still try to run at 1:30, but will be held until 6:00, at which time it will start.
Suspending or holding schedules only affects the scheduled execution of actions. It does not interfere with commands performed in the QRecall application, by the command line tool, or actions that are manually run using the or commands.