Print this page

Explanation around Network Gridforce Jobs Time Zone

Knowledge Article Number 000232647
Description If you have reports based on custom report types that use the Networks object, you might notice inaccurate data in your reports because the log event might have a different time zone than the user’s time zone. 

For example, you might notice inaccurate reporting for the number of posts per day. 
Resolution This issue affects the following custom report types:
  • Networks primary object > Network Activity Daily Metric secondary object
  • Networks primary object > Network Public Page View Daily Metric secondary object
  • Networks primary object > Network Public Visitor Daily Metric secondary object
  • Networks primary object > Network Unique Contributor Daily Metric secondary object
  • Networks primary object > Network Login Daily Metric secondary object
The jobs used in these custom report types gather data from log events. These log event are captured in the GMT time zone. If the user time zone is different, the data collected in your reports use GMT and not the user’s time zone. 

For example: 

If a user’s time zone is PST, and they post at the following times:
January 9: 10 PM
January 10: 7 AM, 10 AM, 11 AM

The events are captured in GMT and logged as:
January 10: 1 AM, 10 AM, 1 PM, 2 PM

The count for January 10th returns 4 because the user’s time zone is ignored.




promote demote