Does this happen only during the start up interval (and shortly after)? If yes, this could be because the location records are loaded by the first worker process in order to have a fast (re)start, at the expense that the saved records are not available immediately.