QRecall subdivides its tasks among multiple processes for security, efficiency, and flexibility.

These processes communicate with each other in order to coordinate activities and monitor progress.

On occasion, these communication channels can break down and you may see a message like "Lost connection with process." This might indicate a serious problem, but it could just be a temporary glitch in the Interprocess Communications (IPC) service. Here's how to tell the difference:

• First, check the log. If the action has logged a completion message (that is, "Capture finished," "Verify failed," and so on), the process finished on its own. The problem was probably a momentary IPC communications problem, and there's nothing to worry about.
• Use the Activity Monitor app to see if the action's QRecallHelper process is still running.

  

  Each running action is performed by a separate instance of the QRecallHelper process. If the helper for the action is still running, the communications between it and the applications monitoring its progress probably just broke down (and may start working again).

  Let the action run; it should finish on its own.

• If there's no helper process for the action, and it didn't record a successful (or unsuccessful) completion in the log, then the process might have crashed. Please send a diagnostic report. The report will include any QRecall related crash logs.

Loss of communications can often happen when the computer is asleep; the action finishes before the monitor process wakes up, so the monitor thinks it has lost communication with the action when, in fact, it was just napping.

If you want to stop an action that the monitor has lost a connection with, you can use the Activity Monitor app to either:

• Quit (not Force Quit) a QRecallHelper process. This is equivalent to clicking the Stop button in the monitor window. If the action is still responsive, you'll soon see a "Stopped" message appear in the log, and the action will gracefully terminate on its own.
• Quit (not Force Quit) the QRecall Monitor process. The operating system will immediately restart it. The monitor will (should) reconnect with all running actions within a few minutes. Once reconnected, resume monitoring the action or stop it, as desired.