@rhessinger The issue was solved with v5.3.10 release. Thank you.