I saw exactly what you saw. I looked through the logs and saw no errors. Older matches from June 20 were showing fine, so it wasn’t a new display bug. I then re-ran the matches for those two encounters, and they completed normally. Here’s an example:
Because I saw the issue but can no longer reproduce it, I think it may have been some kind of network interruption that blocked the machine learning server from handing the match results back to Wildbook. But that interruption seems to have resolved itself. Please let me know if you continue to see this as it is weird that detection results would return without issue but the immediate and subsequent ID jobs would not.