FAQ

The New Version Cannot Start After Migration

Check database connection, configuration compatibility, missing environment variables, image tag, and application logs. If migration has completed, do not directly start the old version unless compatibility has been confirmed.

Migration Reports That a Historical Migration Has Been Modified

This usually indicates that an applied migration file has been changed. Do not edit applied migration files. Restore the correct migration file from the release package, confirm the checksum, and contact support if the database already contains inconsistent migration records.

Model Invocation Error Rate Increases After Upgrade

First remove the upgraded instance from the entry layer, then check Route Policy, channel health, upstream model service status, timeout configuration, and quota policy. After the error rate returns to normal, analyze logs and decide whether to continue the upgrade.

Console UI Shows Old Pages After Upgrade

Check browser cache, Nginx cache, CDN cache, Ingress static resource configuration, and static resource version. Refresh the cache and re-open the Console UI.