Mismatch nested and parent city

Ok, this is sorted now after a new update. I thought that if a city is updated in OSM, and the next day in CS, this would bring the new change into CS, but it seems that is not always the case. There can be a time gap, so the change might not be included this time, but next update instead