Creation Date and Last Updated Date for cases on Inbox does not follow assigned timezone/date
Posted: Wed Jan 13, 2021 2:53 pm
Hello everyone,
I'm working with a ProcessMaker v.3.3.17 enterprise edition and our users have noticed that the Creation Date and Last Update Date in their inbox and draft inbox is up 6 hours. Our server, DB, and front end has the America/Chicago (CST) timezone assigned but whenever you create a new case or update one the date is always up 6 hours.
We checked the env.ini file, the server hour, the DB hour and it all give us our current time and multi_time_zone_support is not enabled so all users should have the same timezone.
This issue comes after we had to restart the HTTP service in our server due to slowness issues not related to number of cases in inbox but we did not find anything in the config files of the HTTP service. Could this be related?
Regards,
I'm working with a ProcessMaker v.3.3.17 enterprise edition and our users have noticed that the Creation Date and Last Update Date in their inbox and draft inbox is up 6 hours. Our server, DB, and front end has the America/Chicago (CST) timezone assigned but whenever you create a new case or update one the date is always up 6 hours.
We checked the env.ini file, the server hour, the DB hour and it all give us our current time and multi_time_zone_support is not enabled so all users should have the same timezone.
This issue comes after we had to restart the HTTP service in our server due to slowness issues not related to number of cases in inbox but we did not find anything in the config files of the HTTP service. Could this be related?
Regards,