# Trends date problem between machines **URL:** \ **Category:** Ignition\ **Tags:** ignition79\ **Created:** [September 10, 2020, 8:20pm UTC](https://forum.inductiveautomation.com/t/trends-date-problem-between-machines/38570 "2020-09-10T20:20:01Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![apimente](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/apimente/32/4030_2.png) [@apimente](https://forum.inductiveautomation.com/u/apimente)\ **Post date:** [September 10, 2020, 8:20pm UTC](https://forum.inductiveautomation.com/t/trends-date-problem-between-machines/38570/1 "2020-09-10T20:20:01Z")
Hello friends, This time We have a problem with trends and the date used for displaying. For example, this is our server (gateway machine): ![imagen](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/3/a31f04da10b674afbfc6f7e2e9988eeb0bb5bb5e.png) As you can see, We were around 4 PM with UTC -4 and daylight saving time. On the other side, We have three clients that show dates delayed. This is an example: ![imagen](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/d/1d2e63c823fdecc7d560621da3b88f22ec74fbc0.png) Same configuration, but our trends were displayed like this: ![imagen](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/9/e97af87bb64e0af3462243cbcaa1c0b604da0c8d.png) The trend save the time in a concatenated format and was something around 4 PM, but as you can see, the blue arrow (meaning NOW) was around 3 PM. The project configuration is this: ![imagen](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/f/4f4d076d9453f303cbe73bda0d60dcfec77b298f.png) So, do you have any idea why this is happening? Do you have any good practice to avoid this? (I read something about use the UTC 0 in every machine, but I don’t know). Finally, I’ts important to know that here in Chile, We applied the daylight saving last weekend. Thanks in advance.