I recently drive to Las Vegas on the 4th and came back on Sunday the 7th and none of the travel miles or points posted to my profile. Or at least I don’t know where to check the life time total. Help. answer please?
Depending on how that trip is broken up by the server, it could take 1-2 weeks to process due to the large distance. We usually don’t even see normal length trips for 3-5 days, and since today is only the 12th, I would be patient and give it another week. Processing all the data from routes is a lot of work.
It probably just hasn’t posted yet.
Although it’s interesting to note that I drove from San Diego to Las Vegas and back July 11th, and the trip THERE has posted to my dashboard but the trip BACK has not. Even more interesting is that I made this exact trip a year prior, and the trip there posted and the trip back never posted. I’ve contacted support about it and they say that they’re hoping that this trip will still post for me, but I’m not hopeful as it never posted last time.
Awesome! Thanks for the answers! Patients is the key 
Still no update. I had a trip from San Diego to Irvine post that I took this weekend. But still no sign of the Vegas trip. 
Seems like a long time now. I would suggest emailing support@waze.com and see if there is something that they can do about it.
Unfortunately I don’t think there is a lot support can do. I emailed them about my missing Vegas -> San Diego trip a few weeks ago, and they just said that they were hoping it would still show up. It hasn’t, and the trip was over 6 weeks ago.
My Vegas -> San Diego trip that was lost a year ago never posted either. You can email support, but I’m under the impression that they can’t do much about it.
This could be one of the reasons Waze has limited the routing distance. Not only does it take the routing server longer to calculate a longer route (and likely to time out) but it seems likely that their system that analyzes the routes, adds route to the archive, assigned GPS points, and assigns permissions could be trouble prone for longer routes.
I agree, likely nothing support is going to do about this since they are relying on the automated process to work correctly. I am sure they ‘could’ do something about it, but that would be a tedious, manual process that they are unlikely to commit to.
The strange thing, though, is that BOTH of the San Diego -> Vegas trips posted with no problems. It was only the return trips (again, spaced an entire year apart) that didn’t post. So I’m inclined to think that it isn’t really related to route length…
Recently seen on the status page in response to a report of missing routes:
Thanks for that, mapcat. I had missed it. Good to know!