Find Answers
Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join Us
Contact
Find Answers
Join Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join Us
Get Support
Have a Question?
Search Qlik's Support knowledge database or request assisted support for your highly complex issues.
Submit a Case
Talk with a Representative
Critical Issues
Experiencing a business critical issue? Please Contact us by phone. Click here to view phone numbers by region.
Contact UsWelcome Guest
Installed Qlik Products
My Environments
Log your environments to ensure faster and more targeted troubleshooting.
View Available Licenses
My Licenses
Understand your licenses to help you maximize your experience.
- ALERT: Qlik Product Download Page Click here
- ALERT: Support Alert Click here
Knowledge
Task reload timestamp changed after upgrade
Article Number: 000060299 | Last Modified: 2020/04/24Description
Qlik Sense systems being upgraded from the June 2017 release to April 2018 or above, task and script logs no longer record log entries with timestamps matching the server time.
Task and script logs now use UTC time.
As of the Qlik Sense November 2019, the format changed further to match that of the rest of the logs, this means that they will once again use server time, but will note the timezone.
Incorrect timestamp in script log
Jira issue ID: QLIK-96515
Description: Timestamp in both script log filename and actual script log did not follow the same standard as other engine log timestamps. Now ISO 8601 is used.
The format that is used is
[yyyy][MM][dd]T[HH24][mm][ss].[SSS][TimeZone]
e.g.
20200420T162000.420-600
Environment:
Qlik Sense April 2018 and newer
Task and script logs now use UTC time.
As of the Qlik Sense November 2019, the format changed further to match that of the rest of the logs, this means that they will once again use server time, but will note the timezone.
Incorrect timestamp in script log
Jira issue ID: QLIK-96515
Description: Timestamp in both script log filename and actual script log did not follow the same standard as other engine log timestamps. Now ISO 8601 is used.
The format that is used is
[yyyy][MM][dd]T[HH24][mm][ss].[SSS][TimeZone]
e.g.
20200420T162000.420-600
Environment:
Qlik Sense April 2018 and newer
Cause
UTC time is preferred to compare machines from different timezones.
Resolution
Working as designed.
Get Answers
Find Answers
Get Support
Have a Question?
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.
Submit a case
Talk with a Representative
Critical Issues
Experiencing a serious issue, please contact us by phone. View phone numbers and hours by region.