It might be possible to cancel the profile removal by properly manipulating table(s) in the database directly before allowing the deivce to get online and conneced to the server.  Don't try anything unless you get explicit instruction from Soti support team responding to your official support case opened at Soti support web site.

Depending on what configuration payload(s) are included in the profile, one POSSIBLE way to reduce the side effect MAYBE is to clone the profile of interest to a new profile of a different name and have it targeted to your device of interest.  When the device gets on line, there might be a chance that the new profile can make same payload configurations deployed before your original profile get removed.  You can then re-deployed your orginal profile again to the device, and then remove the cloned profile.   Before you try this approach on your problematic production device, try the approach with  the above-mentioned profiles on a test device first on your server.  I am not from Soti, and I will not be responsible for any possible data loss or other undesirable consequence(s) on your problematic device. 

Hi Pau,

Thanks for the post!

Is the device online? Perform check-in and confirm the communication between the device and MobiControl server on the logs. You should see 'Device (Agent) checked-in' on the Logs.

And then, please try revoking the pending action and install the profile again?

Regards,