Which version and browser you’re using?
I was having similar issues with Chrome and some of 2016.1 and v8 versions during some processes, also on a vm. Workflow would sometimes fail in unattended runs, worked flawlessly otherwise.
Usual cause was it was trying to access elements before the plugin was activated (when opening new window). Adding a refresh of the page before accessing elements helped as far as I remember.
Yes, that’s true - all UI interacting activities need to be under LaunchWorkflowInteractive, preferably with KeepSessionConnected = True. The Main is started as non-interactive (background).
As far as I’m aware the interactivity does not cascade, meaning that if you have Main → LaunchInteractive → InvokeWorkflow, you’re back to non-interactive part and it might fail. At least that was my experience last time I checked it.
Hi. I know how to solve this. Te reason this goes wrong is that the proccess always start in windows like systems does, that means no ui. And that why i crashes.
When you make a process the only thing you have in main.xaml is an activity - Launch Workflow Interactive, and that point to another xaml file where all the code is in. This activity ensures that the code always runs in the windows mode that have ui. and then it works.
To initiate the robot I use the dos command. Then I close the virtual machine session. The process checks a folder and when a file is received it should ‘launch the workflow interactive’ activity. Are there additional settings to set up?
I don’t seem to find the registry key you mention:
I managed to make the process work by enabling loginToConsole in an invoke process in the middle of the workflow. Well, I’m not sure if it works fully as the process is getting stuck somewhere else, so I’m not sure what will happen when the invoked workflow is completed and in has to continue with the next steps.