Components - Major Outage


We are struggling to get started. When attempting to Play a Record nothing happens at all. Upon investigation via the Platform Monitor I can see a Major outage indicator for the Workspace, Control Tower Applications.

Under monitoring the following checks failed: - SocketTimeoutException - I/O error on GET request for “http://localhost:15280/workfusion/login”: Read timed out; nested exception is - ConnectException - I/O error on GET request for “http://localhost:15580/”: Connect to localhost:15580 [localhost/, localhost/0:0:0:0:0:0:0:1] failed: Connection refused: connect; nested exception is org.apache.http.conn.HttpHostConnectException: Connect to localhost:15580 - SocketTimeoutException -tion: I/O error on GET request for “http://localhost:15280/workspace/login”: Read timed out; nested exception is

These symptoms have occurred on two separate installs

Can you provide instruction on how to progress? Should i send in the or should i look at some logs somewhere?



@Tony_Rae2 - the Control Tower, WorkSpace and OCR services are not launched automatically.

You need to run them using the Platform Monitor tray menu one by one:


Thanks for the reply, much appreciated.

The platform monitor tray was reporting the various components as running. After a few restarts i now have no MAJOR_OUTAGES being reported, although i’m not sure what specifically i did to get to this point.

However, I am still seeing the same symptom which caused me to investigate further originally. When i click “Play recording” nothing happens at all. I can successfully record, but i cannot play it back. I originally thought this was related to the errors previously reported.

Any suggestions of what i may be doing wrong?


you need to check that Bot Manager is up and running.

See Unable to connect with Robot - Error


Hi again,

The bot manager was running, as mentioned the app indicated everything was running. There appears to not be a solution so we ended up uninstalling Workfusion Express.

We have concluded installing as an upgrade from the previous version (1.1.0) to 1.1.2 caused our issues. Now we have installed 1.1.2 directly we are able to finally use the software.

We no longer require assistance on this issue.