# Dataset & daylight saving

**URL:** <https://forum.inductiveautomation.com/t/dataset-daylight-saving/105794>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [May 1, 2025, 6:23pm UTC](https://forum.inductiveautomation.com/t/dataset-daylight-saving/105794 "2025-05-01T18:23:10Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Giuseppe\_Giammo](https://avatars.discourse-cdn.com/v4/letter/g/5f9b8f/32.png) [@Giuseppe\_Giammo](https://forum.inductiveautomation.com/u/Giuseppe_Giammo)\
**Post date:** [May 1, 2025, 6:23pm UTC](https://forum.inductiveautomation.com/t/dataset-daylight-saving/105794/1 "2025-05-01T18:23:10Z")

</div>

Hi everyone. I am observing a very strange behavior with data sets for charts.  
look at the image below..

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/a/fa6ea58e362daafc64b7fb2bba1f057e40029eaf.png)

the system is advancing the daylight saving time creating duplicate . The strange thing is that the original query (below) is in UTC as expected

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/4/54f5c8f4685d5bb6e6c5b05a7c021b75e4ef44a8.png)

is there a setting or a solution to fix this glitch ? the problem is that the chart component will go on error because ... data is not in chronological order...