# ScheduleStart

The date and time at which the schedule should start to run.

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`).

IMPORTANT: The AddSchedule action requires you to provide the schedule information. You can provide the schedule by setting Schedule, or by setting `ScheduleStart` and ScheduleInterval (optionally with ScheduleEnd or ScheduleCount). If you set `ScheduleStart`, you must either set ScheduleInterval, or set ScheduleCount to 1 to run the action once only.

Actions: | AddSchedule EditSchedule
Type: | String
Default: | None
Required: | Yes
Example: | `ScheduleStart=2001-Jan-08 15:42:36`
See Also: | ScheduleInterval

_FT_HTML5_bannerTitle.htm