Invoke Process activity fails when invoked process uses Terminal Session

Feedback Activities
,
1

I have an automation that is using UiPath.Terminal.Activities = 2.7.0.
The automation works perfectly when ran independently. However, when this automation is triggered from an Invoke Process activity in a separate automation the Invoke Process activity never sees the process run complete, although the logs and watching the invoked process run I can see that it completes fine and doesn’t throw any errors.

Is there an issue with Terminal Session and Invoke Process activities?

3

@warren.farmer

Welcome to the community

There is no issue as such…first check what is wrong with process as there either should be an error or should run successfully…it cannot be like no errors and ran sucessful…

Cheers

4

Agreed. The invoked process runs successful. The last to activities are log messages the post, “run successful” and “workflow ended” The log on the automation that has the Invoke Process activity shows both messages, but never progresses. If I use the same Invoke activty to call a process without Terminal Session run fine. I create two test projects. Test1 only have an invoke process activity the calls Test2. Test2 only has a Terminal Session with one function. The Test also fails. This make be think that there is a setting or something within Terminal Sessions that is causing the Invoke Process to not recognize the end of the process.

5

@warren.farmer

there is nothing as such…add more logs and see where is it failing

cheers

6

If the very last activity of the invoked process is a log message stating “process end” and the in the automation that has the Invoke Process is showing that final log message from the invoked process, what other logging needs to be added. it is getting to the end of the invoked process. I can visually watch it open work within and close the terminal session. but the invoke process doesn’t recognize the end of the process.

7

@warren.farmer

you are saying you could see end log and again saying you are unable to see end

cheers

8

So I will try to be more clear…
I have process called “Frame” in this process I have an Invoke Process activity. The Invoke Process activity invokes a process called “Snap.” The process “Snap” ends with two log messages activities, the first post if the process was successful, the second log post “workflow ended”. When ‘Frame’ is ran it gets to the Invoke Process activity and triggers ‘Snap’ process to run. To this point everything is working. Looking at the logs in ‘Frame’ I see that ‘Snap’ process posted the last two messages (Success and End). This tells me the the process ‘Snap’ has run with no error and has completed. Additionally if I watch ‘Frame’ run I can see if trigger ‘Snap’, I can watch the ‘Snap’ process run and see that is completes. When the process ‘Snap’ ends the Invoke Process activity inside process ‘Frame’ doesn’t not seem to recognize this because is never moves to the the next activity in ‘Frame’

To me this shows ‘Snap’ process runs, completes without error, but ‘Frame’ doesn’t see the process end.

9

@warren.farmer

Please check this

Also add more logs at start also and in between to check

Cheers

10

Hey @warren.farmer,
I was able to replicate the described behavior on my side. This seems to be a bug. Thank you for pointing out the issue.
We’ll try to figure out where the issue is and update you here.

Best regards
Bogdan

1 Like
11

Thank you for the support.

12

@warren.farmer, can you please tell me which provider you are using in your terminal session configuration?

13

I am currently using the following parameters in the Terminal Session

Provider: Direct Connection
Show Client = True
Port 23
Type TN5250
Protocol Telnet
Terminal Mode: IBM 3477-FC
Encoding: IMB037

14

Is there a ticket associated with this that I can have?

15

Thanks for replying to my question. It seems this happens only for the Direct Connection provider.

As for the ticket, I suggest contacting the support team and opening a ticket with them. Just link this thread.
I have an internal ticket to track the issue for the dev team but you do not have access to that.