I have several larger updates that we prefer caching before pushing out. We accomplish this by adding the package twice to the same policy. The first one is set to cache and the second one is set to install cached. I've started noticing that the order on several of them keeps changing from caching first to installing cached first. This results in a failure to install a package that doesn't exist yet followed by that package being downloaded. On some policies I can just pop in and fix the order. On others, it immediately resets the order to Install Cached and then Cache. I can't figure out a rhyme or reason for it.
Can anyone help me determine why some policies are reversing orders and others are not?