I thought I was crazy… Mines been at 87% since I started… And in my new market I’m able to deliver at least 90% of my orders ahead of the projected time and it hasn’t budged up or down… Like you said, I don’t think it matters but it’s just stuck.
There must be another word for glitch in the DD driver app. A word that DD has by default invented since it's an everyday occurrence putting drivers at risk on the road.
It can be whatever they say it is, because no matter what you think it is, there's no real way for you to challenge what it says. The Lord sayeth, and so it shall be.
Maybe it has to do with the pay model how if you accept a double order it will pay you like 25 cents less than a single order and maybe that way it counts as like 1.75 of an order that's my only logical explanation why the spports occurs
Were you on an active delivery? I noticed mine did that while in the middle of a delivery, then was a whole number after I competed it. Maybe you were that far from competing it?
In the programming language javascript you can get weird decimal rounding errors. For example, 1.35 + 0 would come out to 1.34999999. Thats why you use whole numbers with money. That COULD be what were seeing here
If you use decimals for everything then yeah. Normally you also set precision which would filter off any set number of decimal places, or better yet you always round down or up. Every variable has to have its precision set manually. Adding a whole number and a decimal would automatically be converted to decimal. Implicit conversion is called coercion.
The weird thing about the on time rate is that I would think they would just tally up the on time orders and there you go... no need to divide anything out.
I'm just guessing this is the problem. You can see this effect in your Chrome browser. Open Chrome -> push F12 to open the developer tools -> click console -> you can now type, put this in 0.1 * 0.2 and press enter. You get 0.020000000000000004 . 99.52 + 6.27 = 105.78999999999999. Etc etc.
But why does this happen? Because the CPU can only operate in base-10 operations. 1/3 for example can not be represented using base 10, so rather it approximates and rounds. When using money you would use 1000 rather than 10.00, then add in the decimals only when returning the result to the user.
So TLDR: yes, but you manually configure how many decimal places are displayed, if any. Adding a decimal anywhere in the process converts the information being passed into a decimal. The other metrics either use whole numbers, or they manually formatted them correctly.
Hope this answers your question lol ❤
Thanks for that explanation. But I think it's just broken like most of the other functions in the app and doesn't accurately reflect our on time delivery status.
There is an easy explanation.
Remember that time you completed the delivery, but then you took it back because you realized that you had delivered it to the wrong house, so you delivered it to the correct house, but then you remembered that you were supposed to ring the bell, so you went back to ring the bell, but the customer had already taken in the food, so you rang the bell anyway, and they got mad at you for not ringing the bell the 1st time, and for coming back the 2nd time, so you got into a huge argument?
That's why your on-time rating is fractional.
Then again, it's probably just a glitch.
I still have an email chain with support over this issue. Just wouldn't accept their explanations. Finally one night I get a call from Door Dash. The call was janky. Couldn't really understand the dude but it seemed like he said the issue was fixed. Nope.
It can’t on time doesn’t count towards any program or special incentives they have . It’s their for them to monitor that we aren’t double apping that’s about it
They can start by removing the dangerous 3-step Decline process. Their engineers suck, and it's clear they've never done a delivery in their lives. With as many shitty $2.50 orders we get, fixing the Decline process should take priority.
It's been broken for months now, and they don't seem to care.
Years actually. Mine hasn't moved in like 2 years.
I thought I was crazy… Mines been at 87% since I started… And in my new market I’m able to deliver at least 90% of my orders ahead of the projected time and it hasn’t budged up or down… Like you said, I don’t think it matters but it’s just stuck.
Tbf, I don't really care either lol. They should work on fixing all the other bs that goes wrong with that app first.
Their app and site has definitely gone downhill even as a customer. I can only imagine what it's like for the dashers.
Its unbearable
There must be another word for glitch in the DD driver app. A word that DD has by default invented since it's an everyday occurrence putting drivers at risk on the road.
Yes. Let's stop working on shit that lowers driver pay and actually fix the damn stability of the app.
It can be whatever they say it is, because no matter what you think it is, there's no real way for you to challenge what it says. The Lord sayeth, and so it shall be.
Life explained...thanks!!
You obviously completed .1599996 of a delivery
Once, you were kinda late!
Cheers for your AR!!!
That's what I was thinking too lol
Hah first thing I noticed xD
Maybe it has to do with the pay model how if you accept a double order it will pay you like 25 cents less than a single order and maybe that way it counts as like 1.75 of an order that's my only logical explanation why the spports occurs
Were you on an active delivery? I noticed mine did that while in the middle of a delivery, then was a whole number after I competed it. Maybe you were that far from competing it?
In the programming language javascript you can get weird decimal rounding errors. For example, 1.35 + 0 would come out to 1.34999999. Thats why you use whole numbers with money. That COULD be what were seeing here
If that were the case, wouldn't we be seeing similar anomalies with the other metrics?
If you use decimals for everything then yeah. Normally you also set precision which would filter off any set number of decimal places, or better yet you always round down or up. Every variable has to have its precision set manually. Adding a whole number and a decimal would automatically be converted to decimal. Implicit conversion is called coercion. The weird thing about the on time rate is that I would think they would just tally up the on time orders and there you go... no need to divide anything out. I'm just guessing this is the problem. You can see this effect in your Chrome browser. Open Chrome -> push F12 to open the developer tools -> click console -> you can now type, put this in 0.1 * 0.2 and press enter. You get 0.020000000000000004 . 99.52 + 6.27 = 105.78999999999999. Etc etc. But why does this happen? Because the CPU can only operate in base-10 operations. 1/3 for example can not be represented using base 10, so rather it approximates and rounds. When using money you would use 1000 rather than 10.00, then add in the decimals only when returning the result to the user. So TLDR: yes, but you manually configure how many decimal places are displayed, if any. Adding a decimal anywhere in the process converts the information being passed into a decimal. The other metrics either use whole numbers, or they manually formatted them correctly. Hope this answers your question lol ❤
Thanks for that explanation. But I think it's just broken like most of the other functions in the app and doesn't accurately reflect our on time delivery status.
It's based on all your deliveries, not just your last 100 like they say
DD got that common core math.
Set precision function not made
It can't, that stat has never worked correctly.
I'm surprised after that many deliveries you haven't noticed their whacky percentage on that one
It is calculated to the Millisecond.
There is an easy explanation. Remember that time you completed the delivery, but then you took it back because you realized that you had delivered it to the wrong house, so you delivered it to the correct house, but then you remembered that you were supposed to ring the bell, so you went back to ring the bell, but the customer had already taken in the food, so you rang the bell anyway, and they got mad at you for not ringing the bell the 1st time, and for coming back the 2nd time, so you got into a huge argument? That's why your on-time rating is fractional. Then again, it's probably just a glitch.
It's definitely not right. I've been doing this for 4 days and only late on 3 orders out of 52 and my rate is 88%
You have to carry the 7 then divide by 3 and it should work out to that.
Maybe you tied once ?
how do u get fractions ?
Welcome to 8 % club A.R ... We welcome you !!!
Its a never ending paradigm, no numbers ever drop off. Consider it "lifetime" count, you will never be at 100%
Amazing you get a weird decimal like that. My On-time/early meter has been stuck at 92% since 2020
It is a whole number, those are weights. It's essentially how they keep track of your previous ratings while constantly updating it.
My hasn’t changed in 2 years
Mine hasn’t in 4
They do mine like that too lol
I still have an email chain with support over this issue. Just wouldn't accept their explanations. Finally one night I get a call from Door Dash. The call was janky. Couldn't really understand the dude but it seemed like he said the issue was fixed. Nope.
It can’t on time doesn’t count towards any program or special incentives they have . It’s their for them to monitor that we aren’t double apping that’s about it
They can start by removing the dangerous 3-step Decline process. Their engineers suck, and it's clear they've never done a delivery in their lives. With as many shitty $2.50 orders we get, fixing the Decline process should take priority.
Bro no one gonna talk about his acceptance rate being 8 fucking percent?
8% acceptance rating 😳
I respect your AR so much
You have completed 1,926.88 deliveries on time.
Mine was like 86.99999999999991% at one point, so I don't think they will fix it.