Applies to Product - Dynamics 365 Lifecycle Services
What’s happening?
The deployment date and time appear differently in the environment history compared to the scheduled date and time.
Reason:
The discrepancy is due to daylight saving time changes affecting the recorded deployment time.
Resolution:
- Confirm that the difference in deployment time is attributed to daylight saving changes.
- Verify the server time settings, as the server operates on UTC. If the scheduled deployment was set for 12 AM and the recorded time shows 1 AM, this indicates a time zone issue related to daylight saving adjustments.