By using execution plans you can control when the task shall be executed automatically by Mail & Deploy Server.
You can manage execution plans by using the following buttons:
|Click this button to create a new execution plan.|
|Click this button to edit the currently selected execution plan.|
|Click this button to delete the currently selected execution plan.|
The following attributes can be set:
|Time Zone||The time zone to apply to the execution plan; all times in the execution plan are always local times according to this time zone.|
|Start Date ||The date-time where you want the next execution of the task to take place.|
|End Date||The end date is optional; if enabled, you can specify until when the execution plan shall be valid. After the end date, the task will no longer be executed on the basis of this execution plan.|
|Maximum Delay||The maximum delay to apply; if the scheduled next execution of the task according to the execution plan lies further in the past than the maximum delay, the task execution will be skipped and the next one in the sequence will be scheduled, until the first scheduled execution is found that is either in the future or in the past, but within the maximum delay.|
|Frequency||The frequency determines how often the task is due to be executed.|
If you choose this frequency, the task will be executed on a daily basis.
If you choose this frequency, the task will be executed on the specified weekdays.
If you choose this frequency, the task will be executed on a weekly basis.
If you choose this frequency, the task will be executed on a monthly basis (this does not equal a 30-day period, but rather to a full month; e.g. April 3rd plus 1 month will be May 3rd). You can optionally choose to stick the execution to the end of each month.
If you choose this frequency, the task will be executed on a quarterly basis, which equals a 3-month period.
If you choose this frequency, the task will be executed on a yearly basis (this does not equal a 365-day period, but rather to a full year; e.g. April 3rd 2018 plus 1 year will be April 3rd 2019; leap years will automatically be recognized by Mail & Deploy).
If you choose this frequency, the task will be executed in intervals as specified. However, you can limit the task execution to specific weekdays.
If you choose this frequency, you can select a calendar (see Calendars) that contains the date-times on which to perform an execution. If you enable Custom Time then you can specify a custom time which will override the ones contained in the calendar; only the dates of the calendar combined with your custom time will be used then.
The logic by which the executions based on execution plans are calculated by Mail & Deploy works as follows: the start date of an execution plan needs to be set to the next date-time at which you want the task to be executed on the basis of the execution plan. Once the task is executed by the execution engine of Mail & Deploy Server (see Server), the date-time for the next execution will be calculated by adding the frequency to the execution date.
Example: You want the task to be executed every Monday at 9:00 AM. To achieve this, you need to set the start date of the execution plan to 9:00 AM of the following Monday and the frequency to "Weekly". Monday, 9:00 AM the task will be executed and the next execution date-time will be calculated by adding the frequency (= 1 Week) to the previously planned execution date (which in this case equals the following Monday, 9:00 AM).
If, for whatever reason for instance, if Mail & Deploy did not have enough execution slots or Mail & Deploy Server was not running at the time of the planned execution the execution of a task could not be performed at the planned execution date-time, the Maximum Delay attribute will be applied. If a free execution slot becomes available or Mail & Deploy Server is running again, then all task executions which could not be completed at the planned execution date-time will only be caught up, if these planned execution date-times are not longer than Maximum Delay in the past.
Example: You have to set up a task that runs daily at 9:00 AM and the "Maximum Delay" attribute is set to 2 days. The last execution of that task has taken place on June 1st and then the server that runs Mail & Deploy Server is shut down for maintenance reasons. On June 4th, 10:00 AM, the server is started again. We can see, that the executions of that task on June 2nd, June 3rd and June 4th have been processed, because the server was down at that time. Mail & Deploy no identifies the earliest of these executions date-times which lie within the "Maximum Delay" attribute, June 2nd 9:00 AM is the first execution date-time to be evaluated because it was the first one that has not been processed; Since the server was started again on June 4th 10:00 AM, June 2nd 9:00 AM lies 2 days and 1 hour in the past; this exceeds the maximum delay, which was set to 2 days. Therefore, this execution is skipped. Then, the next scheduled execution date-time (June 3rd 9:00 AM) will be evaluated; this lies within the maximum delay of 2 days and therefore, the task execution will be initiated once Mail & Deploy server is up and running again.The same applies to the scheduled execution on June 4th 9:00 AM. The next task execution will then be scheduled for June 5th 9:00 AM.