Deployment is coming through Intune via the App Broker. We can see that the software is fully installed on the client machine; however, the App Broker is still reporting it as failed.
What version of App Broker are you using? I believe there was a known issue with the API being used to check for status that was resolved in a more recent release. You may need to upgrade to the latest App Broker release to ensure the status checks are being done correctly.
Additionally, App Broker will monitor status for up to a week by default. If it hasn't received a "success" or a "non-retry failure" by then, it will mark the deployment as failed even if Intune is still trying. This could happen in situations where the client is offline for a while and takes time to actually perform the installation or report the status back to Intune. Check to make sure you haven't changed the default timeout period to something shorter than a week, as that could cause "failures" sooner which may eventually install successfully.
We are currently using App Portal 2025 R2 SP1 (version 20.5.1.0). Thank you, @jdempsey (Flexera Software)​ for your response. It is certainly helpful. I will review this internally to check for any changes or additional observations and will get back to you with an update.
Deployment is coming through Intune via the App Broker. We can see that the software is fully installed on the client machine; however, the App Broker is still reporting it as failed.
@JohnSorensenDK (Flexera Software)​ Could you please help ?
@Satyamk​
What's the error code returned to Intune from the deployment of this device, and is that considered a successful deployment by Intune?
Thanks,
John Sorensen
What version of App Broker are you using? I believe there was a known issue with the API being used to check for status that was resolved in a more recent release. You may need to upgrade to the latest App Broker release to ensure the status checks are being done correctly.
Additionally, App Broker will monitor status for up to a week by default. If it hasn't received a "success" or a "non-retry failure" by then, it will mark the deployment as failed even if Intune is still trying. This could happen in situations where the client is offline for a while and takes time to actually perform the installation or report the status back to Intune. Check to make sure you haven't changed the default timeout period to something shorter than a week, as that could cause "failures" sooner which may eventually install successfully.
We are currently using App Portal 2025 R2 SP1 (version 20.5.1.0). Thank you, @jdempsey (Flexera Software)​ for your response. It is certainly helpful. I will review this internally to check for any changes or additional observations and will get back to you with an update.