With the release v1.16.1, we expected that this issue is fixed. The release was 100% rolled out and the corresponding docker images published yesterday.
Please if your node isn’t in that release, update it, and if it is and you’re seeing this error, report it again.
Thank you so much for your collaboration.