Keep locked - Work Queue

[Anonymous]

What's the function of "Keep Locked " in Mark exception action?

------------------------------
Sanaa Fallah
------------------------------

[KodiSrihari]

Hi @Sanaa Fallah

In the Mark Exception stage , by default the​ Retry and Keep Locked are True . 

As it Executes the stage, it Marks the item as an exception, optionally retrying it by creating a clone of the item into Work Queue as a New Pending item with "Lock Symbol"  in Session Management Environment section.

As Retry is true it will pick the Clone item that is in Lock state , The item must be 'owned' by the calling process - i.e. it must have been retrieved using Get Next Item.

Hope it helps you ,

Thanks,

------------------------------
Srihari
RPA Developer
------------------------------

[devneetmohanty07]

Hi Sanaa,

Whenever you set the Retry Attempts number for a work queue in your Workflow Settings under 'System' tab and you mark an item as an exception using 'Mark Exception' action along with keeping the input parameters for this action: 'Retry' flag as True, that item gets the status updated as 'Exception' and at the same time a clone of that item is created in 'Pending' state which would be picked up later on as per the FIFO algorithm.

However, if in your workflow you immediately want to work on an item the moment it got marked as exception, you can go ahead and send the 'Keep Locked' flag value as True along with the 'Retry' flag as True. What this does is basically it marks the item as exception, creates a clone of that item but the status is 'Locked' instead of 'Pending' so that item is immediately available for you work on.

NOTE: The 'Keep Locked' flag can only be used if the 'Retry' flag is True.

------------------------------
----------------------------------
Hope it helps you and if it resolves you query please mark it as the best answer so that others having the same problem can track the answer easily

Regards,
Devneet Mohanty
Intelligent Process Automation Consultant | Sr. Consultant - Automation Developer,
Wonderbotz India Pvt. Ltd.
Blue Prism Community MVP | Blue Prism 7x Certified Professional
Website: https://devneet.github.io/
Email: devneetmohanty07@gmail.com

----------------------------------
------------------------------

[Anonymous]

So if 'Keep Locked' is True it will give it the priority to the exception item to be worked again but if 'Keep Locked' is False will put the Exception as the last item in the queue, right?

------------------------------
Sanaa Fallah
------------------------------

[Anonymous]

Hi @KodiSrihari

thank you, Could attach the whole documentation you got the photo from

​

------------------------------
Sanaa Fallah
------------------------------

[KodiSrihari]

Hi @Sanaa Fallah,

The Documentation is available for Every VBOs that you select in Action Stage​ -Business Object field , After selecting the VBO the " i " Button available next to that Dropdown field , which navigate to the Whole documentation of the selected VBO.

Attached is the image of the documentation button.

------------------------------
Srihari
RPA Developer
------------------------------

[SamLima]

so the 'Retry' field acts the same when it is True or not specified?
@devneetmohanty07​

​

------------------------------
Sam Lima
------------------------------

[SamLima]

what if I didn't set up number of attempts in system tab and assign mark exception action true in retry field?
@devneetmohanty07 ​

------------------------------
Sam Lima
------------------------------

[devneetmohanty07]

Hi @SamLima,

When you set the 'Retry' flag as True then only the items whenever they are marked as exception will​ generate a new cloned item in 'Pending' state having the 'Attempt' value incremented along it.

So essentially with that being said, if you set the 'Attempts' more than 1 in the queue setting but let say you forget to set the Retry flag as True in your workflow while using the 'Mark Exception' action, then the queue setting for the attempt won't be considered and basically item would just be marked as exception and no new item acting as it's clone would be generated automatically in the queue.

This flag in a way decides if the retry logic as a whole needs to be followed or not. If yes, then it will check from the queue settings how many times do I need to retry in such a case and if no then the item won't be retried at all no matter how many attempts we configure in the queue settings.


Also, to answer our second question, if you set the Attempts field as blank and you set the 'Retry' flag as True then even in that case retry logic would not work since it will be considered that 'Attempts' value is 0 and we need to do a retry attempt at all so the item would be just marked as exception and the flow would proceed ahead.
------------------------------
----------------------------------
Hope it helps you out and if my solution resolves your query, then please mark it as the 'Best Answer' so that the others members in the community having similar problem statement can track the answer easily in future

Regards,
Devneet Mohanty
Intelligent Process Automation Consultant | Sr. Consultant - Automation Developer,
Wonderbotz India Pvt. Ltd.
Blue Prism Community MVP | Blue Prism 7x Certified Professional
Website: https://devneet.github.io/
Email: devneetmohanty07@gmail.com

----------------------------------
------------------------------

[SamLima]

Hi @devneetmohanty07,

I tried to run the bot without setting the retry field to true I left it empty but actually bp retry my exception item with number of attempts from system

​

------------------------------
Sam Lima
------------------------------