# It Stops Working After Update (As Always)
**URL:** https://forum.mautic.org/t/it-stops-working-after-update-as-always/38571
**Category:** Mautic 7 Install / Upgrade Support
**Created:** [September 22, 2026, 8:25am UTC](https://forum.mautic.org/t/it-stops-working-after-update-as-always/38571 "2026-09-22T08:25:48Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@malik](https://forum.mautic.org/u/malik)
#### Post date: [September 22, 2026, 8:25am UTC](https://forum.mautic.org/t/it-stops-working-after-update-as-always/38571/1 "2026-09-22T08:25:48Z")
My Mautic version is: 7.2.0
My PHP version is: 8.4
My Database type and version are: MariaDB / mysqlnd 8.3.30
I installed Mautic via: ZIP
#### **My Problem**
Mautic stops working after an update, in most cases.
It’s a fantastic product when it works fine, but the moment I try to update it, something breaks, always, at least for me! 🫤
And it happened again. Update Mautic from 7.1 to 7.2, and the email builder stopped working. It throws a **500 Internal Server Error.**
**I have faced similar issues multiple times before, including…**
- 404 after update
- Campaign builder stops working
- Email builder stops working
- The CSS gets corrupted
- Can’t create new custom fields
- And a bunch of other issues
#### **Steps I have tried to fix the problem**
- Cleared the cache
- Regenerated assets
- Fixed the permission
- Update schema ([example.com/s/update/schema](http://example.com/s/update/schema)) gives Error 404
But no luck so far; please help!
---
### Author:  [@alexzlobin](https://forum.mautic.org/u/alexzlobin)
#### Post date: [September 23, 2026, 1:37pm UTC](https://forum.mautic.org/t/it-stops-working-after-update-as-always/38571/2 "2026-09-23T13:37:17Z")
Hi @malik,
A 500 error in the Email Builder is not diagnosable from the browser message alone. Please do not continue applying different repair commands yet, as that can make the installation state harder to identify.
The important next step is to capture the original exception:
1. Reproduce the 500 once and note the exact time.
2. Share the relevant error from `var/logs/mautic_prod*.log` and the PHP-FPM/web-server error log at that time. Please remove domains, credentials, tokens, and personal data.
3. Share the output of:
```auto
php bin/console doctrine:migrations:status
php bin/console about
```
1. List all non-core plugins, their versions, and how they were installed.
`/s/update/schema` returning 404 is not evidence that the database update failed. For Mautic 7, database migrations should be checked and run from the CLI, not through that old URL. After taking a verified database and files backup, run migrations only if the status command reports pending migrations:
```auto
php bin/console doctrine:migrations:migrate --no-interaction
php bin/console cache:clear
```
The 7.1 → 7.2 update changes dependencies and frontend assets substantially. A third-party plugin that was valid for 7.1 can still cause a 500 in a builder after the core update. The stack trace will show whether this is a core issue, an incomplete ZIP deployment, a pending migration, or a plugin compatibility problem.
Also confirm that the whole 7.2 ZIP release was deployed consistently. A mixture of files from 7.1 and 7.2, or manually copied `vendor/`, `app/`, or generated asset files, is a common cause of post-update failures.
Once you post the exception trace and migration status, it should be possible to identify the actual cause rather than guessing.