Start automation

1. Confirm DocuTrack and QS1/PrimeCare are open and signed in on that workstation.
2. Click Start. The badge goes ● Starting, then ● Running, and a live log window opens so you can watch progress.
3. In the Merchant Portal, open Transactions. Each processed document appears with its outcome. Anything the agent was not confident about is marked manual review and left for your team.

You can click Stop at any time; it finishes the document in flight and then stops.

The first Start takes longer

Before its first pass the agent checks for Tesseract OCR — the text-recognition component it uses to read the screen — and installs it with winget if it is missing. Allow a few minutes.

This check runs on every Start, not only the first. Once Tesseract is installed it costs nothing; if winget is unavailable on the machine the agent still starts, but logs that every document will route to manual review until Tesseract is installed.

The agent sleeps — it does not stop

When the queue drains, the agent does not stop. It goes to ● Sleeping — next check Mon 08:00 and wakes itself on the schedule you set in the portal. On waking it reopens DocuTrack if needed, re-reads its schedule from the portal, and works whatever arrived.

That means:

• Press Start once, at the start of the day or after a reboot. You do not need to press it after each batch.
• A schedule edited in the portal while the agent sleeps takes effect on the next wake — no restart needed.
• A stopped agent stays stopped. Nothing on the server can start it. If someone clicks Stop, or the machine reboots, a person must click Start again.

Important: This build registers no Windows scheduled task, so automation does not begin on its own after a reboot. If the pharmacy restarts the workstation, someone has to open PharmAutomate and click Start. Configure agent alerts so you find out when a machine is not running.

What a healthy run looks like

• The badge alternates between ● Running and ● Sleeping.
• Transactions fills up, mostly with processed outcomes and a small proportion of manual review.
• The device's Last seen in the portal keeps moving.
• Nobody touches the mouse on that machine.

If a document cannot be completed

The agent retries a document a few times, then skips it, routes it out of the folder for a human, and — if alerts are on — emails a stuck alert. Skipped documents are never silently marked complete.

If the queue still has documents but several consecutive passes achieve nothing, the agent treats that as stuck rather than empty: it alerts, then sleeps until the next scheduled check instead of spinning. That case needs a person.