Meanwhile, at TransDem Labs, an alert popped up on the screen of the on-duty service manager, Frank. Not being idiots, TransDem had incorporated automatic bug-reporting mechanisms into the device, mechanisms which would immediately start sending all log entries and all inputs back to their network. While it would take a short time for the system to connect fully, once it did it would automatically send through all information, with only a couple of seconds lag from that moment.
Frank quickly examined the logs. Normally, errors would simply be recorded, and examined when the team was assembled - most were currently in a meeting, so it would have been hours, maybe even days, before the issue was addressed. But there were a few specific events marked as requiring immediate reporting. One of those, the disappearance of the machine itself, was so critical that the network would even bend the laws of nature to get the last few moments of log prior to disappearance.
Seeing this critical error, Frank called up information on the recipient of the specific unit that had malfunctioned - a record that was kept in a room that couldn't be affected by the Chronivac itself. Jeff, a 16 year old boy, was the current recipient, it seemed. Frank then examined the final statuses of all subjects on the Chronivac. Jeff was now just 4 years old, and his sister was 20. Unfortunately, the original age of his sister had not been recorded.
Frank quickly checked relevant details. The Chronivac, it seemed, had erased itself from existence because it couldn't find an appropriate place in the adjusted reality. Frank sighed - the team had thought they'd fixed that bug already. He quickly constructed an email to the rest of the team to inform them of this issue, then turned back to the problem at hand. Knowing that, without the Chronivac, the recipient could not undo any changes that had been made, Frank followed emergency rule number 14 - in case of major glitching, contact the recipient and if required, revert everything back to the way it was prior to use.
But first, Frank needed to make sure he knew all that he needed to know. He read back over the log, which started with a heap of corrupted data and information on an electrical surge. Recognising this to be a key issue, Frank constructed another email, describing the surge issue, and suggesting that the next model include various safeguards against surges themselves, perhaps including a backup module that would remain separated from the main system's circuitry.
Satisfied that he knew what had happened, Frank loaded the location data into the hologram system, and then stepped onto the projection pad.