UiPath robot not stopping

robot

#1

Hi,

I am using a interactive launch workflow and when it has executed the last activity the robot is not stopping.If I am using a normal workflow launch it is working fine

I have to use interactive workflow only.

How to resolve this issue.


#2

Hi Amar,

Could you please provide Studio version? Also, does it happen with every workflow where you use interactive workflow or only with a specific one?


#3

Do you have Out arguments in that workflow? There were some issues with passing datatables across process boundaries.


#4

Yes I do have out arguments for data table and I cant change them.Is there any way to stop it?


#5

You could try this

And/or upgrading if feasible.

Other than that, I don’t know of a full proof solution.

Probably collecting traces and contacting support wouldnt be a bad idea either.


#6

Hi Andrzej,

I think you have posted a incorrect link.This link is no where related to my issue.


#7

Actually I think it might be.

LaunchWorkflowInteractive works similarly to InvokeWorkflow with Isolated flag - target workflow is started as separated process, arguments are fully serialized and passed through the pipe between caller and callee process.

The hang of the robot you’re describing looks like an issue with passing the DataTable back to the calling process. Pipe limit might be the cause (not necessarily, but it came to mind).

This could also help (indirectly - check the binary serialization as a possible workaround):

How big is that DataTable you’re passing back? (In rows x column)
Does it have any unusual schema or is it built from reading xls/csv file?
What’s your Studio version?

For debugging purposes, could you try:

  • Removing the OutArgument and checking if it works - to confirm it’s the cause
  • Passing a smaller DT (i.e. filter using .Select(someCondition).CopyToDataTable() and checking if it works - to check if the size is the issue

In any case, I’d still say that collecting traces and contacting support could help, as well as provide them another data point to eliminating these kind of issues in the future. Since we can’t rip open UiStudio, it’s hard to say exactly what is happening inside.