Any updates on this issue. Same issue persists for our on-prem instance running of the repo clone
@e2_robert @BYK