PA job is collecting data for incorrect date
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago - last edited 2 hours ago
Hi everyone,
I configured this PA job to collect data for the previous day. However, it is collecting data for two days prior instead. For example, today is 24th Feb, but it collected data for 22nd Feb instead of 23rd Feb.
I have also checked the score sheet, and it is empty for 23rd Feb.
Am I missing something in the configuration?
- Labels:
-
Performance Analytics
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi @digvijaydp3,
I think the timezone might be the culprit here. Your job runs at 2AM and the Run as TZ is None, so it's picking up the system timezone. If that doesn't match your local timezone, the previous day calculation can easily shift by a day.
Quick thing to check — go to sys_properties and search for glide.sys.default.tz to see what timezone your system is running on.
Also try adjusting your relative end from 1 days ago to 0 days ago — having both start and end set to 1 days ago might be causing the boundary issue.
Give that a try and see if it helps! If this solved your issue, please mark it as Helpful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
System Time zone is UTC and my local time zone is IST which is approx. 5:30 hours ahead from UTC. So for me this job runs on 7:30am.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
Since the job runs at 7:30AM IST that rules out the timezone being the issue.
So the configuration is most likely the cause — try updating your relative end from 1 days ago to 0 days ago and run the job again. Having both start and end set to 1 days ago can sometimes cause it to collect data for 2 days prior instead of yesterday.
Give that a try and let us know if it picks up 23rd Feb correctly!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
Hi @digvijaydp3
I also agree with @Schaganti . Your job is running as per System time Zone. It could be the case your local time zone is not matching with System time Zone.
Hence You are getting the issue.
Check the time differences between System Time zone and your time zone. Once job run on that time. check whether its working or not.
