Publish Fail

0
Hello Everyone!I have a Mendix app. In the past, whenever I made changes and published, the app updated immediately on the web. But this time it doesn’t work anymore. I’ve already created a new package, published it several times, cleaned the deployment directory, refreshed with F5, and cleared the browser cache, but the web app still shows the old version and none of my changes appear. It seems like the new package has been created, but the running environment is not picking it up. Could you help me check whether the issue is that the new package was not deployed to the correct environment, the app is still running an old version, or something else is wrong?Thank for your response!
asked
3 answers
0

if it is on a licnesed node, check the default branch line that is configured for the environment you are trying.

there are cases you might be committing to one branch, where as your environment might be picking from a different branch.

And also from environment console check the package name that is being deployed and compare the revision number with your GIT commit revision number.

answered
0

Hi,

Check in Mendix Portal > Deployment Packages whether your new package is marked as "Deployed".

Keep in mind that "Deployed" only means the package has been deployed to some environment - not necessarily the one you are currently testing.

You can also open Details > Deployment Package Details and verify the Name and Version, then compare it with what you expect.

If your latest package is not marked as "Deployed", it means it was created but never actually deployed.

answered
0

Hi,


This usually means the new deployment package is not actually being picked up by the running environment, even though it was created successfully.

Things to check:

1. Verify the correct environment

Make sure you are deploying to the same environment you are accessing in the browser (Dev/Test/Prod). This is a common cause.

2. Confirm package version

In the Mendix Portal:

  • Check the deployment package timestamp/version
  • Ensure the environment is running that exact version (not an older one)

3. Restart the environment

Even after deployment, the runtime may still serve the old version.

  • Do a full Stop → Start (not just Restart)
  • This forces the new package to load

4. Check for CDN/browser caching

Even after clearing cache, sometimes:

  • Hard refresh (Ctrl + Shift + R)
  • Or open in incognito

If using custom domain/CDN, ensure cache is invalidated.

5. Clean deployment (local → cloud)

If deploying from Studio Pro:

  • Click “Clean Deployment Directory”
  • Re-run and re-publish

6. Check logs

Look for:

  • Deployment errors
  • Startup logs showing which version is loaded

7. Multiple instances / load balancer

In some setups, one instance may still serve old version:

  • Ensure all instances are updated/restarted


This is typically caused by the environment still running an older package or serving cached content. Verifying the deployed version and doing a full restart of the environment resolves it in most cases.

answered