Use Cases

First Action Fails—Reaction: Interrupt

Action 1 Check-in
Reaction Interrupt
Action 2 Set State = Green
Action 3 Rename = DEVICEID

Expected result: The check-in action fails unexpectedly, which prevents the remaining two actions from triggering.

First Action Fails—Reaction: Continue

Action 1 Check-in
Reaction Continue
Action 2 Set State = Green
Action 3 Rename = DEVICEID

Expected result: The check-in action fails as anticipated. The RESULT column reflects the issue, while the DEVICES column confirms that next actions executed as expected.

First Action Fails—Reaction: Go to Action

Action 1 Check-in
Reaction Go to action #3
Action 2 Set State = Green
Action 3 Rename = DEVICEID
Expected result: The Check-in fails as expected. The Set State action does not execute because the system skips it due to the Go to Action setting. While two actions fail to execute, the overall rule execution aligns with user expectations.
Note: The system sorts the actions by start time, which causes wrong ordering. For actions that have not started, the system assigns a 'start time' equal to the rule's 'end time.

First Action Fails—Reaction: Retry

Action 1 Check-in
Reaction Retry two times
Action 2 Set State = Green
Action 3 Rename = DEVICEID

Expected result: The Check-in fails three times. The console manages the first two failures through the retry option, while continuing execution handles the third failure is handled by the continue option. All outcomes align with user expectations, and the rule execution is considered successful for the device.

The Rule is Still in Progress

Expected result: Values for the END DATE/TIME, DURATION, and DEVICES columns are available only after the rule completes execution.

If an action has not started yet, the START DATE/TIME column remains empty. If an action has started but not yet finished, the RESULT column remains empty.
Note: Actions are sorted by their START DATE/TIME by default.

Device Enrollment

Normally, each rule generates one row in history. However, enrollment is an exception where many enrollment rules can combine into a single row.
Note: Aggregation begins with the first trigger of the rule when no existing aggregation exists.
Note: Aggregation completes after 20 seconds without waiting for all actions to finish. If actions take significant time, many enrollment aggregations may run simultaneously.

The Same Rule Triggers For the Dame Device

SOTI Connect lets the same rule to trigger many times for the same device. This behavior is intentional and expected.

Red Flags—Possible Bugs

This includes error messages which users do not expect to see.
  • A rule references a device ID that does not exist.
  • A rule processes actions and devices, but some devices have no actions applied by the end of the rule.