option

launchd.agents.<name>.serviceConfig.StartCalendarInterval

This optional key causes the job to be started every calendar interval as specified. Missing arguments are considered to be wildcard. The semantics are much like crontab(5). Unlike cron which skips job invocations when the computer is asleep, launchd will start the job the next time the computer wakes up. If multiple intervals transpire before the computer is woken, those events will be coalesced into one event upon wake from sleep.

Declarations
Type
null or (list of (submodule))
Default
null
Example
{
  Hour = 2;
  Minute = 30;
}