This is often due to a simple and resolvable issue related to the connectivity of the Proactive Monitoring Tool on your gateway machine. This article explains why this happens and how to prevent future issues
Why Automations Fail
Each time an automation is scheduled to run, Abtrace attempts to establish a connection with the
Abtrace Proactive Monitoring Tool installed on your gateway computer. This connection is
essential to initiate and complete the automated recall.
Each time an automation is scheduled to run, Abtrace attempts to establish a connection with the
Abtrace Proactive Monitoring Tool installed on your gateway computer. This connection is
essential to initiate and complete the automated recall.
An automation may fail if:
- The Abtrace tool is not running.
- SystmOne is not running/ not logged into.
- The gateway computer is shut down or disconnected.
When this happens, the system logs the automation failure with a corresponding error message.
How to Ensure Automations Run Successfully
To prevent failures, ensure the following:
1. The Abtrace Proactive Monitoring Tool is running on the gateway machine at the
scheduled time.
2. SystmOne is active and has been logged into on the same machine.
Enabling Redundancy: Advanced Automation API
We understand that keeping the gateway machine always on isn’t always possible. To address this, Abtrace offers a redundancy feature that allows automations to run through other computers if the gateway one is unavailable.
Steps to Enable Redundancy
On each computer where the Abtrace Proactive Monitoring Tool is installed:
1. Click your initials in the top-right corner of the tool.
2. Go to Settings.
3. Toggle “Advanced Automation API” to On.
We recommend enabling this feature on as many computers in the practice as possible.
Example Scenario
Imagine the following setup:
- The automation is configured to run through the gateway computer.
- The Advanced Automation API is enabled on two additional users: Bob and Mary.
Outcome:
- The automation is triggered, but the gateway computer is turned off. It fails there.
- The system checks Bob’s computer, but it’s off as Bob doesn't work on Fridays. It fails
again.
- Finally, it checks Mary’s computer. She’s online, and both Abtrace and SystmOne are
running.
- Success! The automation runs through Mary’s machine.
Imagine the following setup:
- The automation is configured to run through the gateway computer.
- The Advanced Automation API is enabled on two additional users: Bob and Mary.
Outcome:
- The automation is triggered, but the gateway computer is turned off. It fails there.
- The system checks Bob’s computer, but it’s off as Bob doesn't work on Fridays. It fails
again.
- Finally, it checks Mary’s computer. She’s online, and both Abtrace and SystmOne are
running.
- Success! The automation runs through Mary’s machine.
Need Help?
If you've recently enabled the Advanced Automation API and want to re-run any failed
automations, please reach out. We’ll be happy to trigger them manually for you.
If you have any further questions or need clarification, don’t hesitate to get in touch at support@abtrace.co!