You are getting a wrong ordered result when you use loadLocationChildren method from public API on a location, whith content, which is also referenced by another location.

This problem occurs when you are referencing the same content in two different locations.

Steps to reproduce:

1. Create two locations and add the same content to both of it.
   Make sure that in the location tab of the content, you are referencing in both locations, the first location is set as the main location
2. Give the child's of the first location some priority values and doing the same in the second location but with different values for the priority.
3. Set the ordering for both locations to "Sort by Priority" => "ASC".
4. Use loadLocationChildren method in your code to get the child's of the first location.

Result: You will get the child's of the first location ordered by the priority values you have set in the second location

More details can be found here:
forums post