topic Snapshot Isolation Settings for Blueprism Database in Product Forum

Snapshot Isolation Settings for Blueprism Database

SayeedBinAbdullah — Sun, 15 Mar 2026 08:33:45 GMT

Hi All,

Recently we have been facing an issue with our BOT's while after holding a queue item for around 1 hour BOT's through below error, there are total 6 BOT's for this process

error 3960, level 16, state 2, procedure -, line 15, message: Snapshot isolation transaction aborted due to update conflict. You cannot use snapshot isolation to access table 'dbo.BPASession' directly or indirectly in database 'Database' to update, delete, or insert the row that has been modified or deleted by another transaction. Retry the transaction or change the isolation level for the update/delete statement.

Kindly note that "Is Read Committed Snapshot On" is set to FALSE and Allow_Snapshot_Isolation is set to TRUE in the Database,

What shall be the correct configuration for these settings in Database?

Re: Snapshot Isolation Settings for Blueprism Database

naveed_raza — Tue, 17 Mar 2026 11:10:50 GMT

When bot is trying to update same record at same time , that time will get that conflict and its happening because Read committed Snapshot On is FALSE and snapshot isolation is TRUE
SQL Server will protect the data by locking the record.

I think once you set the value to TRUE for Read committed snapshot on option , then it will work .

Re: Snapshot Isolation Settings for Blueprism Database

SayeedBinAbdullah — Wed, 18 Mar 2026 10:11:34 GMT

We did try changing the settings as below and got error during login therefore we had to revert the settings.

Is Read Committed Snapshot On" to TRUE and Allow_Snapshot_Isolation to FALSE

Re: Snapshot Isolation Settings for Blueprism Database

naveed_raza — Wed, 18 Mar 2026 20:35:59 GMT

make sure nothing is running in blueprism , schedulers , bots etc , and you have enable both and then you can try

Re: Snapshot Isolation Settings for Blueprism Database

SayeedBinAbdullah — Fri, 20 Mar 2026 09:48:51 GMT

This being production we shall have accurate information as these settings are manipulated by DBA upon raising a request,

I want to be sure before going back to DBA, that's why I have posted here to know the correct configuration.

Thanks for sharing this Naveed but I will wait for some more time before getting back to DBA.

Re: Snapshot Isolation Settings for Blueprism Database

SayeedBinAbdullah — Thu, 02 Apr 2026 05:37:43 GMT

@david.l.morris @stepher

Appreciate your suggestions on this 🙂

Re: Snapshot Isolation Settings for Blueprism Database

Tejaskumar_Darji — Fri, 03 Apr 2026 05:49:28 GMT

@Neel1 @SouravSaha if you guys have idea on this

Re: Snapshot Isolation Settings for Blueprism Database

SayeedBinAbdullah — Sun, 05 Apr 2026 07:03:21 GMT

@devneetmohanty07 If you can look into this as well.... 🙂

Re: Snapshot Isolation Settings for Blueprism Database

Denis__Dennehy — Tue, 07 Apr 2026 08:56:39 GMT

Over 1 hour is a longer than usual case time for a robot so probably not a scenario well tested by the Blue Prism product team. It sounds like you are seeing database conflicts of some sort because of this case time - effectively you are probably locking a database row for over an hour whereas best practices in databases (at least back in my day) would be to lock for as short a time as possible to avoid oddness.

If your requirements are really one case that takes a robot over an hour to work I would suggest changing your solution to either break this work down and having multiple work queue items for different parts of the work, otherwise change your work queue logic to not maintain the lock - instead have some kind of retrievable key stamp that you unlock but is still only retrievable by the one robot doing that work - this latter idea would also require some kind of clean up logic in case of exceptions because it will not be locked to be included in clean up routines.