When attempting to view details on ~30% of the devices enrolled in a specific environment, the server returns a 500 error in the console. Occasionally, server responds with 404. We can confirm that the devices are properly enrolled and accessible in Jamf Pro and that the issue is not limited to devices with duplicate records.
Issue is limited to one Jamf Pro server in Scout, does not occur to devices in other servers, but also does not occur to all devices in said server.
Update - we can resolve this issue by removing the device from MySQL and allowing it to refresh on the next update. However, we continue to see this issue appear on additional devices over time.
When attempting to view details on ~30% of the devices enrolled in a specific environment, the server returns a 500 error in the console. Occasionally, server responds with 404. We can confirm that the devices are properly enrolled and accessible in Jamf Pro and that the issue is not limited to devices with duplicate records.
Issue is limited to one Jamf Pro server in Scout, does not occur to devices in other servers, but also does not occur to all devices in said server.