Hello dear hasan.ahmed,
thanks for your question.
If I understand correctly, you have a problem with the fact that when you receive a mileage message (as a result of the triggered job), the unit state changes, and the last message time is updated in the unit tooltip and extended unit information. If this is the case, you can disable the "Store counter value as parameter of unit data message" option when setting up the job. Thus, the received mileage message will not affect the updating of unit information.
Also I would like to note that the job to reset to zero/store the GPRS traffic counter has no effect on updating the unit information (tooltip, extended information, state).
I want to add that the task to save the current value of the mileage counter is enough to configure 1-2 times a day, for example, in the morning and evening (or at night). In the report to calculate the initial/final mileage (usually the report is done at least for the day) is enough to get the mileage at the beginning of the day and at the end of the day. All intermediate values are optional.
However, I want to say that earlier we received a request that is associated with such a "virtual" message. They may cause some inconvenience for users, for example, a false triggering of some types of notifications. In this connection, we are thinking about changing the logic of processing such messages. In particular, do not take these messages into account when updating the unit information.
If I misrepresented your problem, please describe your request in detail.
Business Analyst, Wialon