Ok, Ive uninstalled UiPAth again and, after uninstall, I’ve deleted the content of .nuget folder on all users on the machine and, after that, I’ve installed again the stable community 21.10 release: it’s working “ok” now (one of my processes is no more recognizing a login button in a web, but at least processes are opening and running correctly again).
I think it can be good to consider to add to your uninstalling feature that it also delete .nuget folders content on the machines to avoid this kind of issues, I suppose I’m not/will not be the only one who happen.
@Airun I suppose you were installing from an older version that was installed in service mode → nuget packages installed as the service user. Now you changed the installation to user mode and the nuget packages are accessed as your user (with fewer privileges).
Can you please confirm if this is the case? We will try to improve the experience.
@Seldon thanks for your feedback. This is something that was never possible in Studio since when you create Ctrl+K the type is automatically selected to match the declared type of the activity/argument you have selected.
We are looking into improving this so you might see this in a future version.
thanks for your reply, I use this feature from the menu that pops up from the plus button on the right side of the input box, now I know there is a Ctrl+K shortcut, but I still hope this feature can be added back to the menu, thanks
For one use case is that once the robot has extracted the data from a scanned pdf file, the data will then be validated by a human. The data can be forgotten by the human and then stay on Orchestrator for a long time.
Base on that, i think that there should be some mechanism or configuration to get the data moving forward ( either cancel it or auto resume it)
HI @Thong_Mai_Tr_ng_Hoang ,
We are working on SLA feature for Actions that could help you to decide things like force close an Action or re-assign an Action when SLA is breached. But this is in conceptual stages as we speak.
At the moment, what you could do is to use ‘Resume after delay’ activity in parallel to ‘Wait for task and resume’ activity .
The workflow will resume whichever happens first , either when task is acted up on or the specified delay time elapses . You could check if the task is still open, force complete it or perform any other step as per your requirement.