We have a Composite Locator built using the, now deprecated, Create Address Locator tool. The Composite Locator is served out on ArcGIS Server 10.7.1. It has been added to our AGOL org and has been used by our customers, without issue, for many years. Yesterday, we discovered that it is no longer geocoding properly. When attempting to geocode in AGOL using our Composite Locator, AGOL will stop part way through the list of addresses and not process any more of them. I've used two different address lists and get the same results, not all of the addresses geocode. For example, for one list, out of 106 addresses, 27 of them will not match in AGOL; out of the other list of 300 addresses, 151 of them did not match. However, both lists will geocode perfectly in ArcGIS Pro, with only 2 ummatched addresses for the list of 106 addresses and 4 unmatched addresses for the list of 300 addresses. Also, when I search for those addresses individually in AGOL, using our Composite Locator, they are located.
I know it's old technology and we are working on implementing a new environment using the latest ArcGIS Server, this takes time, though. We need to keep this working for a little bit longer.
Does anyone have any thoughts on what may be happening?
