We have been closely monitoring asset-based integration synchronization jobs since the deployment of a fix last night. We are confident that the issue preventing asset app syncs from successfully completing has been addressed. The underlying issue was caused by an exception that occurred when certain fields were filled out and others remained blank in the source data, preventing these app syncs from completing as intended.
If you have any additional questions or concerns please reach out to our support team for additional assistance. Thank you for your patience as we worked to resolve this issue
Posted Jul 25, 2024 - 14:24 EDT
Monitoring
We deployed a hotfix for this issue overnight and kicked off syncs for affected districts. We have seen successful syncs since then but will continue to monitor the situation throughout the morning as a precautionary measure. Thank you for your continued patience and as always please contact our support team with any specific questions or urgent needs.
Posted Jul 25, 2024 - 09:13 EDT
Identified
We are currently aware of an issue causing failed synchronization jobs with our asset-based integrations. Our Engineering team has identified the cause and is working to deploy a solution as soon as possible. We will provide updates here as they become available. Please contact our support team with any specific questions or urgent needs. We apologize for any inconvenience caused by this temporary integration issue.
Posted Jul 24, 2024 - 13:24 EDT
This incident affected: Asset Management Integrations (Jamf Pro, Mosyle, Jamf School, Filewave, Microsoft SCCM).