I encountered a problem in development, and I don’t quite understand why this problem arises and how to modify it. 【18.4.0+Branch.master.Sha.b805b316b1c47ae06c0fe7e619b9c9f96e9e774c Message: Could not retrieve the result of the job execution. This might be because a message was too large to proces…

hmmm not sure how to do this, it typically only happens if the process gets to the end successfully, and that will only happen if all the arguments are active. Bit of a catch 22 :roll_eyes: Also none of them are that large I don’t believe…maybe it’s the combination…

When you log big amount of data like a collection or datatable it is a common behavour. Sometimes it happens even when not logging something but trace mode is enabled. Trace mode is actually another type of loggin so is pretty much the same as logging.If you have such problem, try to increase loggin…

My issue was passing an email message as an argument. It only had one attachment. Solved the issue whilst fixing another issue being unable to delete attachments after sending an SMTP mail. Fix was in this thread Dispose of attachments using below activity with target object being the mailmessage…

In Main.xaml when we are trying to send more data as OUT arguments we will get this of type of error. We won’t invoke main.xaml by other file, It is good practice to avoid arguments. So better declare them as a variables in Main.xaml. If it is really necessary to have the output in orchestrator jo…

Although no orchestrastor, i encountered the same error like you. [image] Error happened when try to get Outlook Mail Messages Help Get the Outlook Mail Messages and output the “Date” by loop process. Error happened like below [image]

Thanks a ton. That solved the issue and saved my day! Not only datatable, for that matter any Output Argument that is not received will throw up this error. I converted Daatatype and Browser arguments into variables to solve the issue.

thanks you very much, the guy from uipath maybe do the customer service…

Message: Could not retrieve the result of the job execution. This might be because a message was too large to process

Help

etss1016 (Tao Tang) January 30, 2020, 2:15am 37

Although no orchestrastor, i encountered the same error like you.

Topic		Replies	Views
Configuring output in a storage bucket - Could not retrieve the result of the job execution. This might be because a message was too large to process Orchestrator orchestrator , question	8	331	May 15, 2024
Couldn't retrieve the result of the job execution.This might be because a message was too large to process Something Else feedback	2	2227	November 18, 2021
Message to Large to process Studio uiautomation	7	202	February 28, 2025
Runtime execution error: message to large Studio	6	1666	July 5, 2021
Message Too Large to Process Exception Help studio , error	1	4094	December 19, 2019

Message: Could not retrieve the result of the job execution. This might be because a message was too large to process

Related topics