When your Automator has been properly installed and paired with your Cuez Project, opening the GUI of the Automator should load the interface in your browser where you can then load your Episodes and automations (or configure automations).
There are a couple situations where the Automator could potentially not connect/load, whether that is right after installing the Automator or even after you have been using it for a while. This article discusses some of these situations.
'Can not connect to the Automator server'
In some situations, you might end up on a screen that states 'Can not connect to the Automator server. Is the service running?', as pictured below. This screen can have multiple reasons.
Or alternatively, your browser could indicate that 'This site can't be reached'. Both screens usually indicate the same sort of issue, with the latter usually showing when reloading the page before following the steps below.
Automator app not running in the background
If the Automator app itself is not running in the background, then the GUI (in the browser) has no Automator to load, resulting in the loading screen.
The solution in this case is normally as simple as starting the Automator application, which will then automatically load your paired Project.
In case the GUI (browser) does not automatically load your Project / Episodes after starting the Automator, then manually refreshing or reopening the GUI should do the trick.
Automator has crashed
In some cases, it could be that the Automator has crashed in the background, meaning it is no longer available to load in the GUI (browser).
The solution in this case would be to restart the Automator, but first verify that there is no Automator application running anymore before restarting it.
Windows:
Check the system tray (bottom right corner) and check for the Automator 'C' icon. If this is still present, make sure to right-click, then quit the application to make sure nothing remains running. Then restart Automator.
Check the Task Manager for any remaining Automator processes and make sure to quit them before restarting Automator.
MacOS:
Check the menu bar (top right corner) and check for the Automator 'C' icon. If this is still present, make sure to right-click, then quit the application to make sure nothing remains running. Then restart Automator.
Check the Activity Monitor application for any remaining Automator processes and make sure to quit them before restarting Automator.
Task Manager (Windows) on the left, Activity Monitor (MacOS) on the right
Crash logs
If the issue was indeed the Automator having crashed, you might get a window saying 'Automator closed - The automator has unexpectedly closed. Please try again.'. This same window will point out that crash logs have been written to a certain folder; please provide us with the crash logs so we can have our team investigate the cause and resolve this in a future update.
The crash logs can be found in the following location:
Windows: The logs should be in
C:\Users\<username>\AppData\Roaming\cuez-automator\logsand/or inC:\Users\<username>\AppData\Roaming\cuez-automator-packagerMacOS: The logs should be in
/Users/<username>/Library/Application Support/cuez-automator-packager
Automator not loading
If your Automator is not loading, but it is not clear if it because of a crash or other issue, the best option going forward would be to quit the Automator, verify that no Automator processes remain, then restart the Automator.