This message was deleted.

Thanks Dennis! We were running this in Dev, and will pull it now.

Ok thanks for the heads up

so glad i never rolled FSL into prod. sad to see this many issues with MS at the helm

I have always wondered, when this kind of thing happens how did they no catch it in test, dev, and ,qa? How is this missed?

I opened a support case re application masking policies’ filters and what I get back was only a link to fls documentation... Support has no clues 😒

That happens to me as well since MS took over. Stinks

There is a “hotfix” build available, that can be requested from the FSL support. Quote from the support forum: “A Hotfix build is now available for this, but is being released more slowly and to early adopters first to ensure higher code quality. Support has been asked to give the release to any customers hitting this issue. Please open a support ticket and let them know that you have hit the 1909 deadlock issue, and they should get you a link to the fix. We hope that some testing improvements, and an early adopter program will help us prevent this type of regression in the future”