It was SR 16213711508. I don't know why there isn't a KB on this...as no one could be running this feature in production with this kind of bug.
