Hello @miliie ,
In Profile Owner enrollment, wiping the work profile removes the entire Android work container. Since the Hexnode app is installed inside that managed work profile, Android may remove the app before it can send the final “Success” acknowledgement back to the Hexnode portal.
Because of this, the work profile can be successfully removed on the device while the corresponding wipe action remains shown as “In Progress” in Action History. Once the Hexnode app inside the work profile is deleted, the device cannot check in again from that work profile to update the final action status.
This behavior is specific to destructive actions where the management component is removed as part of the action itself. It is not usually resolved by restarting the device after the work profile has already been removed, because the app responsible for reporting the status is no longer present in that profile.
In that case, the action status in the portal should not be treated as a guaranteed real-time completion indicator for work profile wipes. The practical confirmation is that the work profile and corporate data are no longer present on the device.
For environments where auditability of destructive actions is a strict requirement, this limitation should be considered during Android Enterprise Profile Owner deployment planning.
Regards,
Simon Scott
Hexnode UEM
What's new 
42 Views
