WooCommerce timezone offset discrepancies in Action Scheduler execution

WooCommerce stores all order-related datetime data in UTC to maintain integrity across various server configurations. While the site-wide timezone setting in WordPress dictates how these dates appear in the dashboard, the underlying Action Scheduler relies on the WordPress cron system to process queued tasks.

A technical challenge arises when the server's system clock differs from the configured site timezone offset. If the PHP environment is not strictly synchronized with UTC, scheduled actions—such as order notifications or stock updates—may trigger at unexpected intervals or experience delays despite the correct display settings in the admin UI.

How does Action Scheduler resolve execution conflicts when the server-level time and the WordPress site timezone are out of sync? Are there specific configurations to ensure scheduled tasks respect the site's local offset rather than the server's system time?