Hi! I've been keeping track of the original issue where the reporter mentioned the problem was introduced in version 1.17.3.
But since this backport was opened, can you confirm whether this might have been introduced in a specific minor version of 1.16?
My team is noticing a similar issue but we're on v1.16, so I'm just wanting to check if it could be impacting us. Thanks!