SCCM Apps updating but deployments not following them

[JustAnotherUser]

Happy to open a support ticket but I assume I've just got something configured poorly.

You can see where the defaults are, application defaults.png

Take this example with the attached screen of chrome.png, it never moved the active deployment.

In the individual app setting there's a small incompatibility potentially where we say override but then we do the same thing as the default, so isn't that just the same?

All I can think of is that we don't check "Do not include version in application name" and maybe that's making it seem them as unique?

[Michael (Patch My PC)]

Hey JustAnotherUser,

I think troubleshooting this will require a look at your Publisher logs, so a support ticket is probably best.

The way your settings are set up should be fine, but I have a feeling that something errored when attempting to move from 130.0.6723.59-->130.0.6723.70 as I don't see that in your list.

The result was the Retaining chain was broken. I'm not sure we'll be able to see what happened as the logs may not go back that far.

Technically, we are not 'moving' the deployment forward, as the Application is being Upgrade In-Place. We are only updating the Deployment Type and the Source files. The Retained version are copies of the Current app that get created .

Going forward, I would recreate your deployment on the latest version and delete the rest. You can utilize our ConfigMgr App Manager to bulk delete the old apps.
https://patchmypc.com/how-to-delete-applications-created-by-patch-my-pc-in-sccm

[JustAnotherUser]

Thanks. Unfortunately, it's not just Chrome but pretty much all applications, maybe all. I just picked Chrome because it's highly visible with all those versions. I'll open a ticket, thank you!