Issue Description
The App "AppBundleID" is not managed.
This could be happening because:
A. If the application is not actively installed on the device and we have the device within the exclusions list. Jamf Pro will continuously try to remove the application from the device causing this failed command.
B. The reason we see Remove app - The app "AppBundleID" is not managed for some applications is due to the application record being within Jamf Pro and the user installing the application manually. Jamf Pro sees the application on the device, Jamf Pro then thinks that the application shouldn't be on the device because the device isn't in the scope of the application record in Jamf Pro. So it tries to remove it. Being that the application isn't managed by Jamf because it was installed by the user, it presents the failed command of, Remove app - The app "AppBundleID" is not managed.
Troubleshooting Steps
For Cause A: Remove the device from the exclusions list within the scope.
For Cause B: Choose an option from below
Add the device to the scope for the application record in Jamf Pro, check the box - make app managed if currently installed as unmanaged
1a. This then adds an application license to the app and makes it managedRemove the application record from Jamf Pro if it is not needed. For example, the Facebook app, if we don't need to deploy this app and users can install it themselves, let them install it themselves and remove it from Jamf Pro so Jamf Pro isn't trying to take over management.
Let the failed commands be there and ignore them knowing Jamf Pro won't be able to remove the app due to the above-discussed behavior. (Note - if we have 17 failed commands for apps, on 1000 devices or more this can cause performance issues depending on the environment. It would be recommended to use option 1 or 2)