Automation Error 2022.10.16

Hi everyone. Can anyone guide to find the root cause?
I receive this error after triggering a process through orchestrator
UiPath studio version 2022.10.16

When debugging in studio this does not occur.
The process initialization looks ok since the first open browser activity does not fail.
Does anyone know what could cause this kind of error?

“Cannot reading properties of null (reading ‘_rawValidators’)”

Hey @nhlapobg23 This error usually indicates that something in a UiPath Form (Create Form activity) is trying to access form field validators that haven’t been initialized correctly — likely because the form is malformed, missing data, or behaving differently in unattended (Orchestrator) execution.

  • Go to the Form Designer.
  • Check if any fields have validators (especially custom ones).
  • Make sure every field is properly bound and has a default value (especially dropdowns, radio buttons, etc.).
  • Export the JSON and look at _rawValidators manually if needed.
    cheers
1 Like

Thank you for your response @singh_sumit unfortunately the process does not use the Create Form Activity. I also cant yet figure out what the process would be validating but I will look again.

@nhlapobg23 ok have you checked logs from orchestrator for this particular process.might be where you can check in which part your process is got faulted..

cheers

Hi @nhlapobg23

please check the below thread

Regards

@nhlapobg23

Welcome to the community

  1. Can you explain a little about what is happening when this error occurs in the bot?
  2. a brief about the process and packages used
  3. How are you triggering the process? and is this a screenshot taken by bot? or is it when you run unattended by keeping machine open you are able to capture it?

these would help us know what might happen..also reviewing the event viewer logs at the time of error also might give you some insights

cheers

Hi @nhlapobg23

Please see if below video helps

Regards
Sonali

Hi @nhlapobg23,

Also, is it possible to run the process in debug mode in production environment to identify the root cause?

Or when you view the logs of this process in orchestrator, which activity is it throwing this error at?

Regards
Sonali