Rule states

You can also view the state of the rules from the RuleEngine pipeline in the Live Status. A rule has the following states:

Rule states 1:

NotInitialized: The configuration of the rule has been read, but the rule has not yet been processed.

Rule states 2:

Initializing: The rule is initializing. The necessary sources are generated in the RuleEngine.

Rule states 3:

Deactivated: The rule is ready for activation. It is not currently running.

Rule states 4:

Activating: The rule will be activated. Any triggers will be started.

Rule states 5:

Pending: The rule is activated. Any triggers have been started. The rule can now be triggered manually. StreamingDataRules go directly from the Pending state to the Starting state.

Rule states 6:

Starting: The rule is starting. The corresponding processing modules are generated and a connection to the data sources is established.

Rule states 7:

Running: The rule runs and processes data.

Rule states 8:

Stopping: The rule is stopping. Stopping is called when the RuleEngine pipeline will be stopped. BatchDataRules also stop when all data has been processed. The rule then switches to the Pending state.

Rule states 9:

Deactivating: The rule will be deactivated. It is no longer possible to start up using a trigger.

Rule states 10:

Invalid: The rule is in an invalid state and must be restarted.

Rule states 11:

Error: The rule is in an error state. This can happen, for example, if a data source (Analytics Logger) is not available. In this case, the rule restarts automatically as soon as the data source is available again. For all other errors, the rule must be restarted manually. This can be done via the Storage Provider Manager or the API or PLC library.