Last added fill up did not update stats

[92teg92]

The fill up I added on 7/4 did not update total miles tracked, or last fill up mpg. Not sure about the other stats these are simply the most obvious. I tried to delete and re add this fuel up but it did not recognize it.

[gantaru]

Similar problem for me. The GasTracker app is not fully syncing with fuelly.com. Today my "Last MPG" did not update in the app but did update on my fuelly.com page. My "Total Distance Tracking," however, did update in the app. My app is version 2.0.3 used on an iPhone with OS 7.1.2.

[gantaru]

EDIT: My "Last MPG" in the app finally did update ... after a six-hour delay.

[bber]

My fuel up from 6/30 is no longer counting in the averages. The fuel up is there just not adding in.

[92teg92]

Upon looking again, it seems its not adding it to any of the averages, the only place my last fuel up is shown is in the log book. This fuel up was added originally with the mobile website, then deleted and added with the desktop site.

[freddie]

Originally Posted by bber

My fuel up from 6/30 is no longer counting in the averages. The fuel up is there just not adding in.

Your fuelup has an odometer of 100000 (ish) whereas your others have 9000 (ish).

[freddie]

Originally Posted by 92teg92

Upon looking again, it seems its not adding it to any of the averages, the only place my last fuel up is shown is in the log book. This fuel up was added originally with the mobile website, then deleted and added with the desktop site.

Fuelups exceeding 4001 miles are excluded from averages. This is the same logic that the old site used.

I can see that you use it to "catch up" a string of missed fuelups. They are excluded at an arbitrary point (4001) as a signal of a fuelup that is invalid. A single fuelup is not meant to be used as an aggregate of many fuelups.

If you broke it into two fuelups, it would work as it stands now.

[92teg92]

Originally Posted by freddie

Fuelups exceeding 4001 miles are excluded from averages. This is the same logic that the old site used.

I can see that you use it to "catch up" a string of missed fuelups. They are excluded at an arbitrary point (4001) as a signal of a fuelup that is invalid. A single fuelup is not meant to be used as an aggregate of many fuelups.

If you broke it into two fuelups, it would work as it stands now.

Good to know, I was wondering if that had something to do with it. I will split it up.


Thanks