We notice the same thing and believe this as a bug. Any workarounds identified ?

Did you find out the reason for this issue ? We have similar issue and looking for some guidance.