Hi Yeswa,
I would suggest you to check few things at your end which will help you out I believe:
First try to use
"Query Lock" action to see if any environment lock with that lock name exists or not, if False then you use "
Acquire Lock" to generate the lock otherwise you can either use Sleep and then retry the
"Query Lock" action again or simply skip the workflow that needs to be run via one bot as shown in the workflow below:
Next, after you execute 'Acquire Lock' action, check your Environment Lock settings under System -> Workflow -> Environment Locks and turn on all the filters at top to "All". This will first give you an idea if your environment lock is generating or not:
If still this issue persists, then you can check the
'BPAEnvLock' table in your Blue Prism Database using SSMS or with the help of someone from Database team if there is one in your organization. You can use the following sample SQL query to check the status:
SELECT [name],[token],[sessionid],[locktime],[comments],[digitalworkersessionid]
FROM [bp_datatabase_name].[dbo].[BPAEnvLock]
NOTE: Replace the highlighted part with your Blue Prism database name which has been setup.
This will return you the columns which you can use to verify if the token is getting generated or not.
---------------------------------------------------------------------------------------------------------------------------------------
Hope this helps you out and if so, please mark the current thread as the 'Answer', so others can refer to the same for reference in future.
Regards,
Devneet Mohanty,
SS&C Blueprism Community MVP 2024,
Automation Architect,
Wonderbotz India Pvt. Ltd.