Orchestrator returns unexpected termination

[9e389f79ff1549b677ac (Mado)]

Hello

My robot seems working fine since the log says the robot execution has ended. But in the Orchestrator it says the process faulted saying the execution ended due to unexpected termination.

What might be the reason?

[Himanshu.joshi]

@9e389f79ff1549b677ac

Can u share the exception message

[9e389f79ff1549b677ac (Mado)]

I forgot to screenshot the message.
The exception is same as above. The robot name is different though.

Do you have any idea? Is this coming from Uipath Robot? FYI the log level of the robot is ‘information’.

Cheers,

[Himanshu.joshi]

@9e389f79ff1549b677ac

This might help

Job stopped due to unexpected process termination

Hello Guys, The cause of this error is the fall of the WCF communication channel between executor and service due to exceeded wcf message size (default is 64Kb). If the workflow exchange messages greater to this value (e.g. logs, arguments, assets) a workaround is to increase the maxReceivedMessageSize in the UiPath.Service.Host.exe.config file: Beginning with 18.2 version the max message size is set to about 1Mb in UiPath.Service.Host.exe.config . Please find the details below and do let us…

[9e389f79ff1549b677ac (Mado)]

Thanks for the infor but the version of my studio/Orchestrator is 18.2.6 so I don’t think it applies to my case.

And also it seems like it is failing between studio and robot. Do you have any thought about this?