Okta scheduled jobs execute in US/Pacific despite tenant time zone settings

Okta tenants outside the US/Pacific time zone have reported that recurring scheduled jobs—such as password expiration policies—do not honor the regional time zone configured in the Admin UI. The scheduler appears to evaluate cron expressions against a service default rather than the tenant's local offset, causing jobs to fire at unexpected times relative to the configured schedule.

This behavior is difficult to validate because the Admin UI displays job times adjusted to the tenant's zone, while the underlying scheduler may use a different reference. API responses return timestamps in UTC regardless of the tenant's display setting, so developers cannot rely on either the UI or raw API values alone to confirm the effective execution window.

Is this time-zone mismatch a fixed limitation of the Okta scheduling engine, or does a tenant-level setting exist to align cron evaluation with the configured regional zone? If the behavior is fixed, what is the supported method for calculating the effective execution window for a tenant in a non-Pacific time zone? Does the Okta System Log or jobs API expose the scheduler's actual time-zone reference so administrators can validate next-run times without waiting for execution?