# ScheduleEnd

The date at which to stop the schedule.

You can specify the date and time in one of the following formats:

- `YYYY-SHORTMONTH-DD HH:NN:SS`. Controller interprets the time as UTC.

- `#ISODATETIME`. An ISO-8601 date, optionally with a time. This format accepts the format `YYYY-MM-DDTHH:NN:SS.FFFFZ`. `YYYY-MM-DD` is always required, but this format accepts the following variations:

  - The year can have a plus (+) or minus (-) sign at the start. A plus sign (+) represents AD/CE years, and a minus sign (-) represents BC/BCE years.
  - The time is optional, and can be to hour, minute, second, or fractional section precision.
  - The date and time can be separated by a `T` or a space, or you can omit the separator between date and time. If you use the `T` separator, it must have a valid time after it.
  - The time zone is optional. If you include a time zone, you can use `Z`, `±HH`, `±HHMM`, or `±HH:MM`.
  - You can omit the separators in both the date and time (that is, `YYYYMMDDHHMMSS`, but not `YYYYMMDDHH:MM:SS` or `YYYY-MM-DDHHMMSS`).

You can also set ScheduleCount to specify the number of times a schedule should run.

Actions: | AddSchedule EditSchedule
Type: | String
Default: | None
Required: | No
Example: | `ScheduleEnd=2014-Jun-30 00:00:01`
See Also: | ScheduleCount

_FT_HTML5_bannerTitle.htm