The Application Usage Report may return entries that appear to be outside the selected date range. For example, a report generated for May 1 to May 31 might include an entry from April 30. This discrepancy occurs due to a difference in time zones between the Application Programming Interface (API) query and the event timestamps. Analyzing the API request and converting the timestamps confirms the report functions as designed.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Reports
• Application Usage Report

A difference in time zones causes the discrepancy. The API query for the report uses the user's local timezone, while the event timestamps in the report use Coordinated Universal Time (UTC), also known as Zulu time. An event recorded late in the day in UTC, such as 2026-04-30T22:23:21Z, falls within the start of the next day when converted to the local timezone of the query, such as 2026-05-01T00:23:21+02:00, so the report correctly includes the event.

How is the report behavior confirmed?

Analyze the API request and timestamps to confirm why the report includes the entry.

1. Retrieve the API request generated by the report.
2. Decode the URL to view the filter parameters. A URL decoder tool, such as URL Decoder, can support this step. The raw URL may appear similar to this:
   /api/v1/analytics/reports/application-usage/exports?filter=eventTimestamp+ge+%222026-05-01T00%3A00%3A00%2B02%3A00%22+and+eventTimestamp+lt+%222026-06-01T00%3A00%3A00%2B02%3A00%22+and+appInstanceId+eq+%22<appInstanceId>%22
3. Review the decoded URL to identify the exact timestamp filters, including the timezone offset:
   /api/v1/analytics/reports/application-usage/exports?filter=eventTimestamp ge "2026-05-01T00:00:00+02:00" and eventTimestamp lt "2026-06-01T00:00:00+02:00" and appInstanceId eq "<appInstanceId>"
4. Note the timezone supplied to the filter, for example +02:00.
5. Compare the filter timezone with the timestamp of an entry that appears outside the range, for example 2026-04-30T22:23:21Z. The Z indicates Zulu time.
6. Convert the Zulu timestamp to the filter's timezone to confirm that it falls within the requested range. A time zone converter, such as Time Zone Converter, can assist with this conversion.
   • In this example, 2026-04-30T22:23:21Z is equivalent to 2026-05-01T00:23:21 in a +02:00 timezone.

Related References

• URL Decoder
• Time Zone Converter