Something looks wrong
The app asked before saving
A question before saving, never a block. It asks about a reading or a price far from the usual, so a digit too many or a lost decimal point is caught before it’s saved.
When it asks
A reading far past the last one (a digit too many?) or one lower than an earlier fill-up gets a question before saving. So does a price far from what you usually pay for that fuel or kind of charging (a decimal point left out turns 3.899 into 3,899), or a charging session over 250 kWh.
So does a date before the car could be on the road (a 2026 model before 2025) or after you sold it, but not an expense’s, which can come before the car or after the sale. So does a fill-up or charging session with the same day, odometer and amount as one already logged (logged twice?).
If a tank reads better than the car can do, History asks whether a fill-up is missing: add it, or say nothing’s missing. One saved twice reads far worse: History asks “Logged twice?”, and deleting the copy puts it right.