Something broke after an update

If you're on Charyl Cloud, updates are health-checked automatically and roll themselves back — a break usually means it already recovered. Self-hosting without a subscription, updates are manual.

What happens next depends on whether your box updates itself.

If you're on Charyl Cloud

Updates already come with a safety net: after applying, every service is health-checked for up to ten minutes, and an unhealthy update rolls itself back automatically, with no action from you. If something broke and then quietly went back to normal on its own, that’s this working as intended.
If you're self-hosting without a subscription
Self-applying, health-checked updates are a Charyl Cloud feature — without a subscription, you update by hand, and you don’t get the automatic rollback. Check the logs for whichever service looks wrong:
```
docker compose logs -f <service>
```
Confirm you're on the version you think you are

“Update now” and your current version both live in Settings → System.

Undoing a manual update

If a hand-applied update is the cause, you can pin SINGER_VERSION (or CHARYL_VERSION) back to your last-known-good release in .env, then pull again — those are the same variables that pin your version in the first place.