# Historian Data is Different 1 Hour #Gateway Current is 6.35 PM #But Data Historian show 5.35 PM **URL:** \ **Category:** Ignition\ **Tags:** ignition81, perspective\ **Created:** [October 29, 2023, 11:49am UTC](https://forum.inductiveautomation.com/t/historian-data-is-different-1-hour-gateway-current-is-6-35-pm-but-data-historian-show-5-35-pm/81132 "2023-10-29T11:49:36Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![chumnan](https://avatars.discourse-cdn.com/v4/letter/c/5daacb/32.png) [@chumnan](https://forum.inductiveautomation.com/u/chumnan)\ **Post date:** [October 29, 2023, 11:49am UTC](https://forum.inductiveautomation.com/t/historian-data-is-different-1-hour-gateway-current-is-6-35-pm-but-data-historian-show-5-35-pm/81132/1 "2023-10-29T11:49:36Z")
Dear All I'm have Problem about Tag Historian is Different 1 Hour on ignition version 8.1.31 #Gateway Current is 6.35 PM #But Data Historian show 5.35 PM Please Sent Solution for Problem Thank you ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/3/33899721c2cf95fe320015294c71d31a30fc2aca.jpeg) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/5/2577dc9a69124b4e3c188877559c311ba14073b5.jpeg) ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [October 29, 2023, 12:08pm UTC](https://forum.inductiveautomation.com/t/historian-data-is-different-1-hour-gateway-current-is-6-35-pm-but-data-historian-show-5-35-pm/81132/2 "2023-10-29T12:08:10Z")
Is the time zone of the designer different from the gateway? If so, the **appearance** of date/time values will be in the designer timezone. ---
**Author:** ![chumnan](https://avatars.discourse-cdn.com/v4/letter/c/5daacb/32.png) [@chumnan](https://forum.inductiveautomation.com/u/chumnan)\ **Post date:** [October 29, 2023, 2:06pm UTC](https://forum.inductiveautomation.com/t/historian-data-is-different-1-hour-gateway-current-is-6-35-pm-but-data-historian-show-5-35-pm/81132/3 "2023-10-29T14:06:49Z")
Dear pturmel Time zone of the designer and gateway is similar I use Asia/Bangkok ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/5/55d5e21a70c3151b049b2c616db8fc2a72e59d1a.jpeg) ---
**Author:** ![chumnan](https://avatars.discourse-cdn.com/v4/letter/c/5daacb/32.png) [@chumnan](https://forum.inductiveautomation.com/u/chumnan)\ **Post date:** [October 30, 2023, 1:57am UTC](https://forum.inductiveautomation.com/t/historian-data-is-different-1-hour-gateway-current-is-6-35-pm-but-data-historian-show-5-35-pm/81132/4 "2023-10-30T01:57:22Z")
Dear pturmel Time zone of the designer and gateway is similar I use Asia/Bangkok ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/0/8083e6de0b3eab7bc8ea72d40c5605a96999424d.jpeg) ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [October 30, 2023, 11:47am UTC](https://forum.inductiveautomation.com/t/historian-data-is-different-1-hour-gateway-current-is-6-35-pm-but-data-historian-show-5-35-pm/81132/5 "2023-10-30T11:47:10Z")
Consider printing out your date/time objects using [system.date.format()](https://docs.inductiveautomation.com/display/DOC81/system.date.format) with a format code that shows the time zone offset used at that point. ---
**Author:** ![chumnan](https://avatars.discourse-cdn.com/v4/letter/c/5daacb/32.png) [@chumnan](https://forum.inductiveautomation.com/u/chumnan)\ **Post date:** [October 31, 2023, 3:43pm UTC](https://forum.inductiveautomation.com/t/historian-data-is-different-1-hour-gateway-current-is-6-35-pm-but-data-historian-show-5-35-pm/81132/6 "2023-10-31T15:43:04Z")
Dear Pturmel I test print time zone according to your instructions, result is picture as attach file. and I recheck time zone of server, gateway, project designer , and database server for store historian. All of the above have the same value. I'm very confused Help me Please. Thank you for support ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/d/edb49e7b59aaad5e05c5da5458c929f4f41dbbf4.jpeg) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/2/426c5e67d904b9689077449cc8ffa91fe2533b59.jpeg) ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [October 31, 2023, 4:23pm UTC](https://forum.inductiveautomation.com/t/historian-data-is-different-1-hour-gateway-current-is-6-35-pm-but-data-historian-show-5-35-pm/81132/7 "2023-10-31T16:23:18Z")
Oh, I see it. You are asking for eight hour-long periods starting eight hours ago. Each row in the dataset has a timestamp for the **beginning** of the hour-long period it represents. Therefore, the last row's timestamp is an hour ago. ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [October 31, 2023, 4:57pm UTC](https://forum.inductiveautomation.com/t/historian-data-is-different-1-hour-gateway-current-is-6-35-pm-but-data-historian-show-5-35-pm/81132/8 "2023-10-31T16:57:40Z")
Good catch! So they need to either change the point count to 9 or change the start date to -7 hours instead of -8 and that should fix it right? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [October 31, 2023, 5:01pm UTC](https://forum.inductiveautomation.com/t/historian-data-is-different-1-hour-gateway-current-is-6-35-pm-but-data-historian-show-5-35-pm/81132/9 "2023-10-31T17:01:40Z")
No, not if they want actual data for the past hour. The dataset is correctly showing the past hour's data in the last row. That hour started one hour before `now()`. So, there's simply nothing wrong, and no timezone error at all. Simply a misunderstanding of what the requested data would "look like". ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [October 31, 2023, 5:09pm UTC](https://forum.inductiveautomation.com/t/historian-data-is-different-1-hour-gateway-current-is-6-35-pm-but-data-historian-show-5-35-pm/81132/10 "2023-10-31T17:09:09Z")
True, and I guess if he wants the current value as well, he'll have to change from point count to periodic and every 1 hour instead to get what he's probably intending to get from his binding. Otherwise point count evenly spaces the points out but starts at the start time, so you'll never get the current value.