@davidacland
Sounds like the record exists in the computers table but not the computers_denormalized table (JSS web interface uses the computers_denormalized table for search and display (faster) whereas the API uses the computers table directly).
To test:
SELECT * FROM computers WHERE udid='YOURUDID-2767-5F47-BF62-8C98EC66A60A';
SELECT * FROM computers_denormalized WHERE udid='YOURUDID-2767-5F47-BF62-8C98EC66A60A';
A jamf recon from that client re-creates its record on the computers_denormalized table and becomes searchable again from the JSS web interface.
I think JAMF should periodically do a consistency check between these two tables.
If you wouldn't mind sharing, would be interested in knowing whether this is the issue in your case.
Thanks, checked the tables and that was the issue. I forced an inventory update and it was back in the web interface.
I guess it would correct itself naturally when the next inventory update occurs if it happened again. Not sure how it happened though.
Thanks again for the quick response.