Community Edition is used for educational purpose and to give some hands on to the developers while learning. It’s not recommended to use the Community edition for actually Client deployments. You will not get any support for Community Edition users from UiPath
Also, this will be problem as well for your Client, as the Community Edition using for Production will also have some legal issue to your client
I suggest you to talk with your Client and get shifted to Enterprise License, to have a smooth run of your Automations
I don’t need any support from UiPath.
All I want to know is : If everything is running fine while developing process, how can process is not working in production. All element are properly found and clicked while developing process but same process is not working in production as element are not found.
yes, it is in unattended mode.
All click were perfectly working during testing.
but same click is not working in production at 2nd run.
At 1st run in production everything was working fine but at 2nd day which was 2nd run, Process could not find same click.
which problem is this ? UiPath or mine ?
We cant decide like that…would suggest checking the screenshots and see if required screens are pressent…then in the error it would give you the closes match as well check if the closest match is similar then may be there are selector changes…
Try using some delays there might be network deays as well…increase the timeout and check
First thing is verify the screenshot properly to see if right screen is present
Maybe this can be handled by using the Auto Update Policy that is present in the Cloud :
We cannot really say this , It is UiPath’s Software and eventually we would have to depend on UiPath support if any of the suggestions here does not work. Similarly in terms of using the software as well, we would have to abide by the legal terms. Check the below post as well on using Commmunity in Production Environment.
We will However be able to provide help on the automation level.
Could you let us know if you are still able to test the process and does it work while testing using the Studio ? Are you testing directly in Production or Dev Environment ?
What are the different changes observed during the 2nd run ?
Again if you test it in Production does it work fine first time and next times does it give the errors? Also, Providing Log Details/Error Message also would help us to come to a conclusion.
The answers provided before were already quite detailed, so I will just add a small remark.
On a quick look, it looks like your issue is mainly about selector not being robust enough.
Alternatively, in case your unattended machine is a different environment than your development one, then it could be that the other environment is not identical and causes the selectors to be different (simple example would be a situation where you would use English names in your selectors on the development machine but the ones on your unattended machine are in a different language).