In rare cases, the Deep Security Agent(DSA) may send a heartbeat to Deep Security Manager(DSM) after it receives the move command. The DSM would then consider that the agent failed to activate in Cloud One - Workload Security and it will set the move status to Move Failed (Failed to activate). The DSM will expect a heartbeat but after the default of two failures it will mark the status of the DSA as offline. However, the DSA is actually moved to the Cloud One - Workload Security and actually has an online status. This should rarely happen and it's only a UI bug and would not break any agent functionality.
- Deactivate the agent from the Deep Security Manager console to change its status to "Unmanaged".