Last updated
An issue was identified where Geo Centroid attributes could be returned inconsistently between the REST and SOAP Parse APIs following a Tomcat service restart, despite using the same input data, role, and locale.
The behavior depended on which service was invoked first after startup, resulting in differences in attribute availability due to initialization and caching inconsistencies between the REST and SOAP service layers.
This release addresses the issue and ensures consistent Geo Centroid attribute responses across both APIs, regardless of service startup sequence.
Last updated