This has been fixed. We are tracking this as WB-768, and we have seen it twice now and have a sense of what is causing it and why. While I’m working on a fix, I echoed the call back result from detection (which was successful), and this time the server accepted it. I am now seeing the detections.
Thanks,
Jason