After upgrade processes does not run the same in dev and prod environment

Help Something Else
, ,
1

Hi,

Not sure where to post this, but if someone could direct me, that would be awesome!

We have recently upgraded our UiPath from 2019.10 to 2023.4, and while we upgraded our dev environment first and tested our processes, everything ran fine. Then we proceeded to upgrade our prod environments, and now when we run these same processes in prod, we get errors occurring which never and still doesn’t occur in the dev environment.

The studios are all 23.4.4 and the orchestrators are 2023.4.1

Does anyone know what the issue may be?

Please and thank you!

NOTE: Some processes run fine and as expected, while some do not in prod, but is fine in dev.

2

There are a few possible reasons why your UiPath processes are running fine in development but failing in production after upgrading from 2019.10 to 2023.4.

One possibility is that the development and production environments are not configured in the same way. For example, the development environment may have different versions of .NET Framework or other software installed.

Another possibility is that the production environment is experiencing performance issues. This could be due to a number of factors, such as insufficient resources or high traffic loads.

Use the UiPath Diagnostics tool. The Diagnostics tool can help you to identify and troubleshoot performance issues with your processes.

https://docs.uipath.com/studio/standalone/2023.4/user-guide/diagnostic-tool

Cheers @itsonly_annie

1 Like
3

Hi @itsonly_annie ,

I believe we do see that the issue happens only for some of the Processes, In that case, Maybe there were packages/dependencies not yet uploaded (apart from the normal packages) to the Orchestrator and hence it may be failing ?

As it is debugged and understood the issues are happening for some processes only (first phase testing), Picking it one by one and checking the issues or errors specifically on it could also help in understanding the cause.

4

Thank you for that - will definitely try the dianostic tool out!

I have discovered that it seems the problem is mainly occurring in the “Element Exist” action in MSEDGE of the process, and even with changing the element several times, it still won’t “see” it on screen in prod, but can “see” it in dev.

The UiPath extension is on for both prod and dev - do you think this issue is related to a difference in .NET Framework and etc.? Or could this be something else?

Again, all processes utilise the “Element Exist” activity, but it seems to fail on the processes that use MSEDGE on the prod machines, but not dev. Both dev and prod are on MSEDGE Version 118.0.2088.46 (Official build) (64-bit)

Thanks for the help!