Tasks and status

From saving a setting to the terminal result

bg-dots
bg-dots

The queue in device details helps follow an operation. It provides Active («Активные»), Queued («В очереди»), and History («История») tabs, counters, and a refresh action.

Operation stages

Observation Meaning Next check
A setting was saved The server accepted the change within the scope of its response Was a task created for the intended device?
A task appeared The operation was scheduled for execution Is there a final result?
A task completed An execution result is displayed Does the terminal configuration match the expected value?
The terminal is online There is current confirmation of a connection The specific task result and readiness of the required feature

Online status does not confirm command execution. Offline status does not prove that a previously sent command failed to execute. An empty history for one terminal does not mean there are no tasks in the system.

Verifying the result

  1. Open the target device and identify the operation by action and time.
  2. Check active and queued tasks, then history.
  3. Compare the final response with the original change.
  4. Inspect the actual terminal configuration and, for integrations, the final connection result.
  5. When changing a shared profile, repeat the check for each target device.

A dash in a time field should not be treated as a creation time, an absent task, or a confirmed error. Clarify unfamiliar status meanings for the deployed version.

Disconnection or waiting

Refresh the view and inspect history after reconnection before retrying. Repeating an action may have side effects; a missing first response does not establish that retrying is safe.

If the outcome is unclear, record the time, device, task, expected setting, and observed state. See troubleshooting for the handover procedure.

Debug events and the interface connection status do not replace a user activity log or confirmation of execution on the terminal.

Profiles Integrations