At the May 27, 2020 meeting of Dev/Pri, we decided to close this issue since it only occurs during changes made directly to the database. Therefore, anyone encountering this issue must have enough familiarity with the backend that they can fix the problem without a background job in the staff interface.

The specific case this issue arose from was an apparent import error that assigned an erroneous name_person_name_order value to nearly 13,000 agent records. This resulted in the auto-generated sort name to omit the "rest of name" field. Batch correcting the name_person_name_order value leaves the agent records with the incorrect sort name.