Went past a petrol station today which I last passed 6 weeks ago. Nobody else seems to have input a price in the meantime. So I put in the new price and got:
Note the message saying it’s waiting for someone else to confirm the price.
Sure enough, asking the price for the station again comes back with:
So despite my telling Waze the new price, it still insists on informing everyone of the old price.
I suspect there is an issue with the petrol price module…
I have just passed a garage that I know I updated this morning. Price was 5 days old!
Updated and got 8 points! Checked, 5 days old but I was the updater.
Updated, and got more points (seemingly). Still on the old price.
It may be worth noting that the old price is exactly the same as then new one ( I think!).
This is a new message (for me) seemingly saying that another Wazer will have to input the same price before it shows. Now that might be fair enough in a city with lots of Wazer’s, so that two or three people pass the station each day. However, where more than a month elapses between anyone trying to put a price in, it makes the feature totally useless.
It’s bad enough that prices should be out of date because no-one has put them in recently, but that is inevitable. The implication of this message is that someone at Waze HQ has taken a deliberate decision to make matters worse. :evil:
I had this problem a while ago, when the Waze backend started forgetting how long some of us had been using Waze, and was applying baby wazer restrictions on our price entries… I haven’t noticed any problems with updating prices recently, so it’s more likely to be another temporary glitch affecting just some of us than a general policy being applied to us all.
I can’t see any point in restricting people’s ability to input petrol prices. I can see why map editors should have to experience using the SatNav for a bit before being allowed to edit, but I can’t see why driving more miles would make someone any better at typing in petrol prices.
Since Waze seems to be over-complicated and bug-ridden in this area, why not allow everyone to input prices? Then it would matter less that Waze frequently loses track of the status of the user.
And as an aside, if “baby Wazers” aren’t to be allowed to put prices in, it would be more polite to tell them up front, rather than invite them to type up the prices and then reject them. I wonder how many people have deleted the Waze app in annoyance at being so patronised?
I believe baby Wazers are told to foxtrot oscar when they attempt to input prices at the report/fuel prices point, so they’ll never get to input a price and then be rejected…
You’re right, I was getting mixed up a little here. I found the thread where I mentioned this “price confirmation” message when it happened to me - getting on for a year ago, so no wonder my memory of it was a tad hazy…
I just realised the wrong petrol price on Monday. I’ve updated some petrol price where I nearly update them daily but some how some of them says last updated 5 days ago, etc. and the updater is me or someone else. Some price are correct but some are not. I’m not sure it happens after I updated the beta version or server issue.
Yes. Don’t think it’s anything to do with who input the prices, I think it’s a server/database issue.
At the moment, quite often the date/price on the list headed “Around You” or “Along Route” is different from the date/price you see when you select a station and press “Info”. Furthermore if you go back to “Location” and forward again to “Info”, you are quite likely to see the date/price change. So far as I am aware, the prices are always correct for the date given. But of course you want the latest date and the price that goes with it.
My guess is that some part of the system is not very good at refreshing it’s cache to pick up the latest price. I think it’s at the Waze server end rather than the phone end. If the problem was with the phone app, I think each user would always see the same price. I think the price you get each time depends on which particular Waze server you get, and how old the cached data on that server is.
Yet another Waze bug :roll:
Mind you, it’s easy for us end users to get frustrated by the bugs, and not appreciate that most of the system works very well indeed most of the time.
Got a slightly different, but probably related, problem. If I use the “Not offered” button to clear a price as part of a station update, the next time I visit that location the removed price is still shown even though the rest of the details have been updated OK.
I have come across a couple of stations which have had issue, they did resolve after a few days.
Strangely, at the weekend I edited a garage to update it to Shell from Total. An hour or so later I actually visited to get petrol there and it had already been updated to a Shell garage!!
2 weeks later, the problem is still present. It’s the station here which has been ignoring my requests to remove the Super UL price.
As an experiment, this morning instead of trying to remove the price I tried submitting a price that would ordinarily throw up a range error, and instead got this:
So something isn’t right with the way this station is being handled by the server…
Seems like setting the price to 0 has allowed the station to start behaving correctly again - drove by yesterday morning and noticed another user had been able to update the prices correctly, with Super UL being shown as N/A for the first time in ages…