Outbound lists commands the ERP has queued back to a device — enrolling an employee on a biometric unit, sending a print job to a printer on your network. The gateway collects them on its next check-in, so delivery is a queue rather than an instant action.
Where to find it
Go to EdgeBridge > Outbound.
What the list shows
| Column | Description |
|---|
| Gateway | Which gateway the command is for. |
| Command | What the device is being asked to do. |
| Payload | The detail sent with it. |
| Queued | When the ERP raised it. |
| Delivered | When the gateway collected it. |
| Status | See below. |
Statuses
| Status | Meaning |
|---|
| Queued | Waiting for the gateway to collect it. |
| Delivered | The gateway has it. |
| Acknowledged | The device confirmed it acted. |
| Failed | It could not be carried out. |
A command stuck at Queued means the gateway has not checked in — not that the device refused. Look at Last seen on Gateways before investigating the device itself.
What queues a command
| Action | Produces |
|---|
| Enrol employee on device | An enrolment command, so the device id is assigned by the ERP rather than guessed from an existing enrolment. |
| Printing through a gateway | A print job aimed at a printer on your own network. |
| Command to device | A command you raise by hand. |
Related pages