Workload Orchestrator FAQ

Estimated reading time: 4 minutes

Frequently Asked Questions about Workload Orchestrator:

[Hosted Only] Where is my registration verification email?

I tried to register as a new user on Workload Orchestrator, but I never received the verification email. I clicked resend several times, but still haven’t received an email. What does it take to get the email?

  • Check your email spam folder. Customers often find the email in their spam folder.
  • Emails should be received within a few minutes of the registration.

Why don’t I see device attributes, such as manufacturer and model number, in the device INFO tab?

  • These attributes are sent by the devices. There is a special OMA object designated for this purpose. Also, a user can update them in the Device Details form.

What could be some reasons that my device is not connecting?

  • Try double checking your connection parameters.

  • If the parameters are correct, check your firewall settings. 

Why can I see device data in the RAW tab, but not in the EXPLORE tab?

  • Data sent to Workload Orchestrator must be in a special format, as shown in the JSON schema in the Project settings page. If Workload Orchestrator cannot parse incoming messages, the messages only appear in the Raw tab.

How can I remotely manage a device?

  • Workload Orchestrator supports two protocols to remotely manage a device: LWM2M and MQTT.


  • A Workload Orchestrator specification that enables device management.The Explore tab for LWM2M devices supports WRITE/EXEC operations, so Workload Orchestrator can directly manage LWM2M devices.


    Workload Orchestrator supports 3 types of MQTT topics:

    • request - to send manage requests to a device
    • response - to receive responses from a device
    • data - to receive data from a device

    Request/response formats are not defined.

    For example: If you can program your device to reboot when it receives {“command”: “reboot”} from the request topic, you can reboot your device remotely.

    If you open the MQTT tab on the Device Details form, you can see Request/Response tabs to manage MQTT devices online.

    To accomplish management tasks, you must program your device.

    The Batch Device Management feature offers operations similar to those described above, but you can define batch commands (MQTT or LWM2M) and schedule these commands to execute against a group of devices.

How can I delete a Project?

Are messages sent from OT Link Platform to Workload Orchestrator Secure?

  • We prevent security issues through LWM2M, REST, and MQTT protocols. They only use secure transports, such as TLS and DTLS. We do not support unencrypted transports between the two products.
  • All security credentials established during cloud activation are securely stores on the OT Link Platform device and they are not exposed to the end user. It is impossible to alter these credentials after activation as long as physical security of the OT Link Platform Converged edge system is maintained.

What is the difference between Workload Orchestrator Alerts, Events, and Incidents?

  • Alert - The Workload Orchestrator Alerts feature allows a user to define notifications based on rules. Rules comprise a set of conditions that define an abnormal state of a device. For example: No data received from a device in more than two minutes, or the temperature went below 30 degrees.
    First, define Actions. Actions are the types of notifications, such as Slack or Webhook. Then, create a Trigger. A trigger is a combination of device tags, a set of rules, and an action. Once triggered, Workload Orchestrator sends the alert notification to the defined destination. Alert notifications can be viewed on the Workload Orchestrator dashboard as well as from email and third-party web applications, such as Slack.  The Incidents tab on the projects page lists the alerts that were generated. 
  • Event - Events list the Workload Orchestrator configuration activities that occurred for a project within a company. For example: Added a new project, or deployed a new device.
  • Incident - If a device reaches an abnormal state according to the rules, then Workload Orchestrator will create a new incident and send notifications. The Incidents tab lists the alerts that were generated. When a device returns to a normal state, the open incident will be closed and Workload Orchestrator will send another notification with an incident resolved message.