Hello again.
The fix for this was just merged into main as well as stable, and should be included with your next deploy.
main
stable