Hangfire enqueue serializable level

[MantasAudickas]

Hello,

I have read previous posts about serializable isolation level:

Hangfire.SqlServer defaults write isolation level to Serializable

Hi, We are enqueuing jobs withing a read committed transaction but this is failing because underneath HangFire.SqlServer is using a Serializable isolation level. I was wondering if this Serializable isolation level is something that is absolutely required, and if not what would be the best way to make it configurable. Thank you

Currently we have some troubles regarding this. The problem is that our transaction isolation levels are in most cases read committed. In order to enqueue new jobs we need to enclose calls to hangfire to “RequiresNew” transaction scope. This is not very good approach in case our transaction fails.

Is there any plans to make it usable in parent transaction without changing level? Maybe I can also investigate on this problem with deadlocks in hangfire itself if there is no plans to introduce this by someone else?

regards
Mantas