Hi @daniel-scati , thanks for the analysis! We'll get this fixed via PG-2635 in an upcoming maintenance release (hopefully 2024.2), which is targeted for next Friday.