If you use geocoding data integration rules be careful with the bypass triggers and bypass work flow rules options.  One (or at least me) would think that those meant the data.com user that updates the lat/long would bypass triggers and workflows, but it doesn't seem so.  I checked bypass triggers and when a user changed a city value, the trigger that should have fired did not.  Unchecking that fixed the issue.

@Admin Group, Raleigh, US @Solo Admins @All Dreamforce @Salesforce Automation Hour