This bug occured a few weeks ago, where PrismaticConstraints with low LinearResponsiveness do not reach their target when moving from a higher target to a lower one:
I’m assuming the flag that caused this has been re-enabled, but the issue still persists.