Rotation of a constraint is not taken into account for limited range movement

Rotating a constraint does not update its range of motion based off of angular limits. The user who reported this also mentioned that migrated constraints do not see this issue (eg: migrating a physics asset with constraints made in 4.20 to 4.21 works without an issue) but rotating them after migration to a version where this issue is present makes it occur.

Regression?: No
This occurs in 4.21.
This is however a regression from 4.20 where it did not occur.

1. Import a Skeletal Mesh (Exported TutorialTPP and imported it again for this test)
2. Open the physics asset
3. Delete all generated physics body
4. Create two bodies on two different bones with intention to create a constraint between (I used upperarm_r and lowerarm_r for this test)
5. Select one of the bodies and add a constraint on the other's bone
6. Set the parent physics body to Kinematic
7. In the Constraint, set two of the Angular Limits to Locked and set the other to Limited
8. Press simulate and notice the movement along the constraint.
9. Rotate the constraint along the axis that is currently set to Limited to change the limited range
10. Press simulate
    Results: The results do not change and the range of movement stays the same
    Expected: The range of movement matches the newly rotated constraint.

I am not able to find world outliner how to enable it?

Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows

How can i modify the param name in EQS node

How does TextureRenderTarget2D get TArray<uint8> type data?

What method is used to fill polygonal regions when drawing spline mesh at run time?

Delay nodes occasionally don't fire the "Completed" output in a nativized build

When I open UE4 4.24.3 it appears that. Does anyone know how to solve?

Error UE5 5.0.3

How does UMG set overlapping layouts?

How to achieve HLSL Multiple Render Target in Material blueprints?