I don't think the issue is that MX is updating, I think the issue is that MX is still initializing. There is a bit of a difference. The MX XML is failing to apply correctly the first time as the MX framework is likely still initializing and is not ready for the the XML to be submitted by the Agent. The distinction here is important because you couldnt key off a version of MX as an assignment filter criteria to solve for this problem as the MX version will already be higher as a result of the A11 upgrade. It is not upgrading itself any further after the A11 upgrade, it is already updated by that OS upgrade. I therefore don't think you'll be able to solve this problem by looking for a property that you can key off of as a filter criteria since what you're dealing with is more of a state of the device (MX framework not being fully initialized and ready to receive configurations) versus a property of the device (ie. MX version)


Newer SOTI agent versions have tried to work around these timing issues by inserting validations in the startup sequence of the agent to prevent any attempted configuration submissions until after the MXMF framework has loaded. You've likely even seen these splash screens appear as the agent is loading as they often can get stuck for some time. The 2024.x+ agents should therefore already have a solve for your problem built in. I'm wondering if maybe you're not upgrading the agents until after the devices have upgraded to A11. If you were to upgrade the agents to a newer version while they're still on A8 and then upgrade them to A11 it may solve this MX XML application failure.