# Update failed for some reason?

**URL:** https://meta.discourse.org/t/update-failed-for-some-reason/222611
**Category:** Self-hosting
**Created:** [March 30, 2022, 9:28pm UTC](https://meta.discourse.org/t/update-failed-for-some-reason/222611 "2022-03-30T21:28:15Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Benjamin\_D](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/benjamin_d/32/277831_2.png) [@Benjamin\_D](https://meta.discourse.org/u/Benjamin_D)
#### Post date: [March 30, 2022, 9:52pm UTC](https://meta.discourse.org/t/update-failed-for-some-reason/222611/2 "2022-03-30T21:52:09Z")

</div>

Hi,  
this seems related to

> [@Recovering from failed/partially applied upgrade](https://meta.discourse.org/t/recovering-from-failed-partially-applied-upgrade/221924):
>
> I attempted to upgrade my Discourse instance, however due to a handful of issues, it seems to have failed in a partially applied state. When running ./launcher rebuild app, I get the following error message, which indicates to me a migration that was already (partially) applied: I, [2022-03-24T21:13:16.043071 #1] INFO -- : \> cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' rake aborted! StandardError: An error has occurred, this and all later migrations canceled: PG::Dup…

and

> [@Recovering from failed/partially applied upgrade](https://meta.discourse.org/t/recovering-from-failed-partially-applied-upgrade/221924/2):
>
> You can do a
> 
> ` ./launcher start app`
> 
> To start the old container. That’ll get you back up.

seems this commit didn’t fix the previous issue ?  
[https://github.com/discourse/discourse/commit/8040b95e8c4abeab1ab9fe50826f92c52995a814](https://github.com/discourse/discourse/commit/8040b95e8c4abeab1ab9fe50826f92c52995a814)  
and

---

_[View the full topic](https://meta.discourse.org/t/update-failed-for-some-reason/222611)._