Whenever we click Save button of sn_hr_core_case form, the sys_updated_on has additional 5 hours

[Michael Galang]

Hi Experts, 

Whenever we click Save button of sn_hr_core_case form, the sys_updated_on has additional 5 hours added
For example: if the current time 2026-08-31 7:09:50 PM, the sys_updated_on value in xml is showing 2026-08-31 12:09:50 PM. The instance current time zone is set to America/CST. 
May we know how to fix it? 

I would appreciate your feedback regarding this matter. 

Thank you very much! 

[Ankur Bawiskar]

@Michael Galang 

the instance always store time in GMT/UTC

So the value you see on list/form for sys_updated_on is in your local time zone

May be your timezone has 5 hours difference when compared to GMT

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Michael Galang]

Hi Ankur, 

Thank you for your response. However, it seems we need to raise the issue to HI team since the affected Save button is OOTB. 

[Ankur Bawiskar]

@Michael Galang 

if it shows the current time on Updated on column on list after you save then it's working as expected

[IbrarA]

Hi @Michael Galang 
the value is fine, it's just a display conversion. sys_updated_on is always stored in UTC and gets converted using the timezone on your own sys_user record, which overrides the instance default in glide.sys.default.tz. Check yours at avatar → Preferences → Language & Region (screenshot below); for CST/CDT it should be America/Chicago, which is UTC-5 in August and UTC-6 in winter. That's also why the gap looks like 5 hours on some records and 7 on others, since different users touched them from different timezones. In script, gr.getValue('sys_updated_on') gives you raw UTC while gr.sys_updated_on.getDisplayValue() converts to the session user, and XML export shows UTC where reports and list exports show the converted value.

Thanks