Troubleshoot
The connection test fails
- Symptom
- The AutoOps setup window shows a red error after you click Test connection.
- Cause
- The key may be copied incorrectly or may belong to a different shop.
- Fix
-
- Copy the key again from the AutoOps Site Setup area.
- Confirm you are using the key for the selected shop.
- Paste it into TracsConnect without extra spaces.
- Click Test connection again.
- When to contact support
- Contact support if the same key is confirmed in AutoOps but still fails.
The wrong shop appears connected
- Symptom
- The connection saves, but the workflow appears tied to a different location.
- Cause
- A key from another AutoOps shop may have been pasted.
- Fix
-
- Open AutoOps Site Setup for the correct shop.
- Copy that shop-specific key.
- Replace the saved key in TracsConnect.
- Run a controlled test for that location.
- When to contact support
- Contact support with the shop name and the AutoOps location you expected.
The setup window does not show expected AutoOps behavior
- Symptom
- AutoOps is saved, but staff do not see the workflow they expected.
- Cause
- The workflow may not be part of the current AutoOps rollout for the shop.
- Fix
-
- Confirm the shop is included in the AutoOps rollout.
- Confirm you have permission to manage or view the workflow.
- Test one known appointment or workflow before expanding usage.
- When to contact support
- Contact support with the shop name and the workflow you expected to use.
When to contact support
Section titled “When to contact support”Send support the shop name, the workflow you tested, and the error shown in TracsConnect. Do not send the AutoOps key.