I am running into the exact issue as described in this post thread.
The reply was from Nov 17 and said that this was a known bug which would be fixed soon. I have implemented the solution described in the link but I am curious if this bug has not been fixed yet or if I have run into some new bug. For your reference or debugging, detailed information is in the secure note below.