Waze forum

Just check this sticky post first and then you can contact support via a help form on the Support page (appears after you do a search without resolution):

http://www.waze.com/forum/viewtopic.php?f=18&t=23084

Read a little closer: not all drives. Some showing up, some not.

fvwazing wrote:Longer drives take longer to process - shorter drives take precedence in processing. In a few days you will see all your drives.

Actually, I don't think it's that either. I did 2 long drives (113km) yesterday. The first one hasn't showed up but the second showed up almost immediately. The exact same drive from 3 days ago is missing in both directions.

----
Waze Area Manager
City of Toronto, Ontario, Canada

AlanOfTheBerg wrote:Did you submit any map issues in the missing drive ?

I don't think so. But I'll keep that in mind next time I notice a missing drive.

zexpe wrote:My current theory is that these are drives that were shared with friends _and_ a friend actually viewed the link.

Not mine. Haven't shared any drives at all.

WeeeZer14 wrote:2.) Data compression is turned on by default now. Client must be caching data to compress chunks and send. So it is possible we lose the buffer on shut down if it isn't successfully flushed.

I had always had Data Compression on in the previous version and never noticed this behaviour of missing drives, though.

jasonh300 wrote:Or it could be the latest beta.

That certainly can't be ignored.

jasonh300 wrote: I mean that the latest beta might've fixed it.

Yep - that's what I understood.

jasonh300 wrote: Is anyone with missing drives using Android or are we all on iOS?

In this thread? It's about the iOS app version 3.5. Prolly wont get many responses from Android users, I'd think!

just ran into this on my phone - however i had connectivity issues at the beginning of the drive, not the end, which was my return trip home - the trip there showed up fine however. would love to help find any rhyme/reason behind this!

CBenson wrote:

jasonh300 wrote:My theory is that if you end a drive and Waze can't immediately make an internet connection to upload the drive, the drive gets lost.

But you shouldn't lose the whole drive. At worst shouldn't you only lose from where you lost the internet connection.

1.) URs may be involved in that it means there is more data for the drive thus more data to upload.
2.) Data compression is turned on by default now. Client must be caching data to compress chunks and send. So it is possible we lose the buffer on shut down if it isn't successfully flushed.

If buffer is based on size alone, it may be good to change to size OR time if the size is fairly large (say over 10 minutes worth of driving).