Hello - I have a frustrating problem. I created a Blue Prism process over 6 months ago that was heavily used for some time, then we had to pause it as it completed its task. It was importing data from some software into a different version of the software (the software i'm automating does not have an import feature and no APIs). I populate the Blue Prism queue with information such as name, address, email, etc - basically it fills out a form.
The last change to the process was back in June. It did run in September without any problems. We are now using it again - but it seems to become "stuck" in a bad loop of sorts when it runs in headless mode. I schedule the import process so it can run overnight and most of the day.
It does seem to be running. The software I'm automating has a Search option to check for duplicate entries. If it finds the entry already exists, it marks the queue that the item was found and goes to the next entry. The problem is - it starts marking every entry as having a duplicate entry (except for the first 2-3 - these are working). I manually checked some of the entries it reports as being found - they do not exist in the system.
If I run the process in the Blue Prism IDE so I can observe it, it is working perfectly. I do not see any errors. I have tried this on my laptop and also on the production system that normally runs Blue Prism. When I switch over to running it "headless", this is when the problem occurs.
Any ideas on what I might check? It works fine when I run it and observe it. It works for a few times and then gets stuck when Blue Prism runs it without the IDE. I am using login agent for headless mode.
The last change to the process was back in June. It did run in September without any problems. We are now using it again - but it seems to become "stuck" in a bad loop of sorts when it runs in headless mode. I schedule the import process so it can run overnight and most of the day.
It does seem to be running. The software I'm automating has a Search option to check for duplicate entries. If it finds the entry already exists, it marks the queue that the item was found and goes to the next entry. The problem is - it starts marking every entry as having a duplicate entry (except for the first 2-3 - these are working). I manually checked some of the entries it reports as being found - they do not exist in the system.
If I run the process in the Blue Prism IDE so I can observe it, it is working perfectly. I do not see any errors. I have tried this on my laptop and also on the production system that normally runs Blue Prism. When I switch over to running it "headless", this is when the problem occurs.
Any ideas on what I might check? It works fine when I run it and observe it. It works for a few times and then gets stuck when Blue Prism runs it without the IDE. I am using login agent for headless mode.