Show the diff for "The latest configuration has not been applied"

[Geczy]

to reproduce, visit a project that's "outdated" ? and see this message, but no clue as to what exactly has changed, and why we need to redeploy

The latest configuration has not been applied
Please restart (or redeploy) to apply the new configuration.

[nev1d]

+1. I have exactly the same problem and I have no idea where these changes happened

[Jihad]

+1. I believe i have a service stuck on this. Restarted multiple times with pulling images again. Same.

[steff-mat]

Please mention the Coolify version, the service(s) which are affected and if it was deployed via Applications (Git/Docker Based) or from the Databases/Services list.

[Jihad]

@steff-mat Thanks! I might not be original poster, but with me, i'm on:

• Coolify v4.0.0-beta.367
• Happens on Services list: Grafana, Metabase, n8n-with-postgresql
• Doesn't happen on: cloudbeaver (from service list)

restarted them couple times, still getting it. Even with pull latest & restart. Not sure if a can get logs or do manual check of configurations vs. current to know what's going on.

[jhgeluk]

I started to experience the same on:
v4.0.0-beta.370

[sergiotapia]

Same on v4.0.0-beta.380 seems stuck there?

[Gog0]

Same for me on v4.0.0-beta.394 with a newly installed firefly app. It started after I made database public I believe.

[djsisson]

Just press save and then restart

It computes a hash of all the various settings and fields for a project and compares that with a saved value

So when upgrading versions if a new db column is added or a default setting is changed, the hash now won't match, pressing save will fix the warning.