I have a critical app update sitting in my required apps list, but it has not pushed out to all the devices in the policy yet. If the system tries to update the app and it fails for some reason, how often does it actually retry? I just want to understand the retry loop and how often it checks for these pending updates before I start troubleshooting further.
11 Views
Replies (3)
Marked SolutionPending Review
Participant
4 weeks ago
Apr 23, 2026
Marked SolutionPending Review
The retry behavior really depends on a few different factors. Are we talking about a public store app or a custom enterprise app? What OS are these devices running? Also, how exactly are you pushing this app out? Are you relying on a Required Apps policy, or did you try pushing it manually via the Install Application remote action?
Marked SolutionPending Review
Participant
4 weeks ago
Apr 24, 2026
Marked SolutionPending Review
Sorry, I definitely should have included that information. These are iOS devices, and the app is Tablet Command. It is a standard public store app, and I am pushing it out using a Required Apps policy.
Marked SolutionPending Review
Participant
4 weeks ago
Apr 26, 2026
Marked SolutionPending Review
Got it. Since Tablet Command is deployed via a Required Apps policy, the system natively checks for updates periodically every 3 hours.
If an update attempt fails because the device is temporarily offline, locked, or has a spotty network connection, the system does not get stuck in a hyper aggressive infinite retry loop. It simply falls back to that standard 3-hour sync cycle. Once the time elapses, the system checks the device compliance, sees that the required app is still outdated, and will attempt to push the update again automatically.
Save
