Hi all,
I've hit a bit of a road block with the background run mode and executing multiple processes at the same time.
For some background, this initial part of the process grabs emails (via MS Graph), download attached PDFs and sends them to Abbyy FlexiCapture for OCR.
This is initial part is split out across two different processes as the FlexiCapture part is a hybrid between what we call a "collector" and "executor". They have been built in a way that allows us to run them both at the same time across multiple digital workers which has been achieved using environment locks and work queues (PDF data is stored in the work queue itself along with the email object returned from MS Graph).
This works fine most of the time, however I'm seeing a number of exceptions every now and again to do with one of our shared environment variables:
"ERROR: Internal : Environment variable not defined".
I've confirmed that the EV definately exists, and its certainly not removed at execution time as this EV forms part of our downtime process and is used across all of our other processes built in Blue Prism (simple true/false flag, decision at the start of the process that ends the process if this is set to true).
Has anyone had issues before like this and able to offer any advice?
We have requested an upgrade to 6.10.6 to resolve a large number of issues that we have had since updgrading to 6.10.5.
Regards,
------------------------------
Jordan Harvey
Norfolk County Council
------------------------------
