# 7.3 Trending Issues **URL:** \ **Category:** Ignition\ **Created:** [October 17, 2011, 1:52pm UTC](https://forum.inductiveautomation.com/t/7-3-trending-issues/3445 "2011-10-17T13:52:35Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Duffanator](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/duffanator/32/3560_2.png) [@Duffanator](https://forum.inductiveautomation.com/u/Duffanator)\ **Post date:** [October 17, 2011, 1:52pm UTC](https://forum.inductiveautomation.com/t/7-3-trending-issues/3445/1 "2011-10-17T13:52:35Z")
Hey guys, I’m noticing some troubling issues in the new trending displays on version 7.3. Take a look at this trend: ![](https://us1.discourse-cdn.com/inductiveautomation/original/1X/0a37c1e6c1262d14273ecbb08352a5cf5d682126.PNG) The green line is the motor speed of this line. The motor ramps up fairly quickly to 60 Hz and then stays there until it’s shut off, but when it’s displayed on the trend it looks like a gradual increase in speed until the conveyor shuts off then goes to zero. From what I saw and read on the changes made to 7.3 it looks like Ignition is doing this to save time and resources. On a small scale of time this is fine, but over 2 and a half hours it makes the information useless, now everyone is going to think that the conveyor gradually increased in speed when it really did not. Is there something I have to do to change how this is displayed or is this how it is now? ---
**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\ **Post date:** [October 17, 2011, 4:48pm UTC](https://forum.inductiveautomation.com/t/7-3-trending-issues/3445/2 "2011-10-17T16:48:21Z")
Hi- You’re right, this behavior isn’t correct. It’s a problem with the value storage, and we should be able to get it fixed for 7.3.1. In the mean time, the only way you can really correct it would be to insert a 0 value for the tag right before the time it starts. Unfortunately, this might be a bit tedious… which is why I’ll try to get this fixed as quickly as possible! Regards, ---
**Author:** ![Duffanator](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/duffanator/32/3560_2.png) [@Duffanator](https://forum.inductiveautomation.com/u/Duffanator)\ **Post date:** [October 17, 2011, 5:34pm UTC](https://forum.inductiveautomation.com/t/7-3-trending-issues/3445/3 "2011-10-17T17:34:45Z")
Thanks! No one has noticed it yet, but I’m sure it’s just a matter of time before I start hearing about it 😛 ---
**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\ **Post date:** [October 17, 2011, 8:40pm UTC](https://forum.inductiveautomation.com/t/7-3-trending-issues/3445/4 "2011-10-17T20:40:00Z")
This has been fixed for 7.3.1. The behavior would still be the same if using “opc timestamp” mode in conjunction with analog tag mode, but in that case, you would probably want to change the tag mode to discrete. Regards, ---
**Author:** ![Duffanator](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/duffanator/32/3560_2.png) [@Duffanator](https://forum.inductiveautomation.com/u/Duffanator)\ **Post date:** [October 21, 2011, 1:34pm UTC](https://forum.inductiveautomation.com/t/7-3-trending-issues/3445/5 "2011-10-21T13:34:45Z")
I upgraded to 7.3.1 yesterday and the trends look much better now. Thanks for getting this fixed!