Table Of Contents
RunMode
Last Modified: February 7, 2020
Specifies how the master runs this schedule: Continuous (0), Once (1), or Null (2).
Usually, the default value for the run mode is Continuous. If the schedule is configured to be a collision resolving table for an event-triggered entry, the default is Once.
Data type: 
This property is a ring (enumerated list) with the following values:
| String | Value | Description |
|---|---|---|
| Continuous | 0 | The master runs the schedule continuously. When the last entry executes, the schedule starts again with the first entry. |
| Once | 1 | The master runs the schedule once (all entries), then returns to the previously running continuous schedule (or null). If requests are submitted for multiple run-once schedules, each run-once executes in succession based on its Priority, then the master returns to the continuous schedule (or null). |
| Null | 2 | All communication stops immediately. A schedule with this run mode is called a null schedule. |
This property is not read from the database, but is handled like a database property. After opening the database, the default value is returned, and you can change the property. But similar to database properties, you cannot change it after a session is created.
Where This Property Is Available:
Desktop OS: Windows
FPGA: Not supported
Web Server: Not supported in VIs that run in a web application