# Aborting a deployment purposely stalled in the ArtifactReboot\_Enter state **URL:** \ **Category:** General Discussions\ **Tags:** state-scripts, mender-client\ **Created:** [June 8, 2022, 4:45pm UTC](https://hub.mender.io/t/aborting-a-deployment-purposely-stalled-in-the-artifactreboot-enter-state/5009 "2022-06-08T16:45:41Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![kadler](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kadler/32/1635_2.png) [@kadler](https://hub.mender.io/u/kadler)\ **Post date:** [June 13, 2022, 3:21pm UTC](https://hub.mender.io/t/aborting-a-deployment-purposely-stalled-in-the-artifactreboot-enter-state/5009/3 "2022-06-13T15:21:25Z")
Thanks for the suggestion. It looks like the Update Control framework should work well for most update flows. If the user initiates reboot or shutdown, a hook can use the DBus API to tell Mender client to continue to `ArtifactReboot`. The only case I can think of where the use of a pause prior to `ArtifactReboot` will not work is if the user abruptly cuts power to the device – in that scenario, Mender client will rollback the update. A related question – do you know when Mender client 3.3 will be released? I’d like to build pauses into deployments via Mender server, but I’m seeing failures related to issue [MEN-5421](https://tracker.mender.io/browse/MEN-5421) in versions 3.0 and 3.1, and unrelated failures in version 3.2, which may be related to problems described in this Mender Hub thread: > [@Mender keeps rolloing back after update](https://hub.mender.io/t/mender-keeps-rolloing-back-after-update/4705/15): > > Im having the same Problem. Downgrading to version 3.1.0 solves the issue. This forces me to use mender-connect 1.2 which has a bug losing connection to the server quite often. --- _[View the full topic](https://hub.mender.io/t/aborting-a-deployment-purposely-stalled-in-the-artifactreboot-enter-state/5009)._