# Ability to restart failed jobs due to permissions

**URL:** <https://drone.discourse.group/t/ability-to-restart-failed-jobs-due-to-permissions/9313>\
**Category:** Drone Support\
**Created:** [May 23, 2018, 5:05pm UTC](https://drone.discourse.group/t/ability-to-restart-failed-jobs-due-to-permissions/9313 "2018-05-23T17:05:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jhernandez](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/jhernandez/32/4244_2.png) [@jhernandez](https://drone.discourse.group/u/jhernandez)\
**Post date:** [May 23, 2018, 5:05pm UTC](https://drone.discourse.group/t/ability-to-restart-failed-jobs-due-to-permissions/9313/1 "2018-05-23T17:05:34Z")

</div>

Currently you can’t restart a job that has already failed which make sense but errors due to permissions like `privileged: true` in a step are fixed by marking the repo as trusted in the UI but you still need a commit to trigger a new build. Is there a way to force a restart for this particular case?

---

<div class="post-metadata">

**Author:** ![bradrydzewski](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/bradrydzewski/32/3513_2.png) [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)\
**Post date:** [May 23, 2018, 5:29pm UTC](https://drone.discourse.group/t/ability-to-restart-failed-jobs-due-to-permissions/9313/2 "2018-05-23T17:29:49Z")

</div>

> Currently you can’t restart a job that has already failed

hmm, this is not true. You can definitely restart a failed build (I do it often). You can inspect the restart endpoint here to see the exact logic: [https://github.com/drone/drone/blob/master/server/build.go#L473:L683](https://github.com/drone/drone/blob/master/server/build.go#L473:L683)

EDIT: ok I understand, you want to restart an `errored` build (not a failed build). No this is not currently possible in the drone user interface. You can, however, re-trigger the hook in github which will re-run the build, without having to create a new commit.

---

<div class="post-metadata">

**Author:** ![jhernandez](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/jhernandez/32/4244_2.png) [@jhernandez](https://drone.discourse.group/u/jhernandez)\
**Post date:** [May 23, 2018, 6:21pm UTC](https://drone.discourse.group/t/ability-to-restart-failed-jobs-due-to-permissions/9313/3 "2018-05-23T18:21:44Z")

</div>

Thanks yes, usually regular users don’t have access to webhooks but that works.

---

<div class="post-metadata">

**Author:** ![bradrydzewski](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/bradrydzewski/32/3513_2.png) [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)\
**Post date:** [May 23, 2018, 6:48pm UTC](https://drone.discourse.group/t/ability-to-restart-failed-jobs-due-to-permissions/9313/4 "2018-05-23T18:48:20Z")

</div>

Looking at the code for 0.9, which has undergone significant refactoring in order to support multi-machine pipelines, these restrictions appear to no longer exist. So it is likely when 0.9 is released this will be a non-issue. Cheers!