It seems that it’s a similar issue with the below, so let me share the post here too hoping someone - who are interested in dealing with this irritative limitation - can lead us to the solution.
I encountered the same issue and from what I remember, what cause the crash is not retreiving the data but serializing the log (or writeline) onto a log message (UiPath serialize all logs).
First solution and the simplest one when you have logs for a quite good amount would be to use the write text file activity to log the string.
You can then log log the textfile path for further reference if necessary.
Second option which is slightly more elegent is to :
Use Deserialize Json activity
Loop Through each Jtoken as as it suits you (of type Newtonsoft.Json.Linq.Jtoken)
Log each token string
Here you have an example of log using Orchestrator API where i separated queues items
Running a HTTP request in debug mode throws an error. To solve this issue, the maximum log message size needs to be increased. This can be done by editing the [InstallationFolder]\UiRobot.exe.config file and adding the
Hi Florent_Salendres,
Would this help in the case XML string size as well? If yes, could you guide me further on where I need to add this statement in the file?
You can try appending the config file as in the image given before with the highlighted line. Furthermore, change your logs to “Information”, otherwise your job will fail because the log limit exceeds.
is there a solution that doesn’t involve messing around with config files? It’s over 2 years since the last post on this topic and I have the same issue.
It causes an error after the http request because the jobject isn’t set correctly. I have tested this and it only occurs on long inputs => long outputs.
I am trying to user an AI to analyse emails, and these can get lengthy quickly. This is causing me an issue.
Hey @aksh1yadav I have tried to do ctrl+f and I still cant find “ExecutorServiceBinding” I am running 2020.4.1 version studio, do you think that might affect it?