Not sure at what version of the terminal activities pack this started to happen, but when waiting for screen text via Wait Screen Text if it hits the timeout and I catch the exception the terminal session that was being used gets disconnected. Anyone else experience this or know a way around this. Studio version 2023.10.4, Terminal.Activities 2.7.0 - 2.8.0 it happens on all of them, Windows project.
Hi @trwalsh, we are aware of the issue and it will be fixed in the next version of the Terminal Activities package, 2.8.1 estimated to be released around the end of October.
In the meantime, there is a workaround:
- Save the terminal session in a variable of type TerminalConnection - use the output connection property in the terminal session where the connection is established
- Surround the WaitText activity in a try/catch
- On exception, if the connection is closed, InvokeCode activity with
conn.ConnectionChanged(ConnectionStatus.Connected, TerminalResultCode.Success )
, where “conn” is the saved connection.
The above workaround will not interfere with the bug being fixed in future versions of the package.
An example on how it can be implemented:
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.