Synapse Monitoring Displays Pipeline Run Times One Hour Behind After Time Zone Migration

Recently, Alberta adopted a permanent Alberta Time (ABT, UTC-6) standard, eliminating seasonal daylight saving time changes. As part of this change, we updated our Synapse triggers and validated that they are running at their expected schedules.

Although our pipelines are running at their expected scheduled times, the Pipeline Runs monitoring page is displaying the Run Start time one hour behind the actual execution time.

For example, a pipeline triggered by our 9 AM Trigger FA is shown in the monitoring page with a Run Start time of 8:00 AM, even though the trigger executed at 9:00 AM as expected.

We have performed the following validation:

• Windows time zone is configured correctly to Alberta time.
• Azure account regional settings are configured correctly.
• Synapse triggers are configured and executing at the expected schedule.
• The issue occurs in both Google Chrome and Microsoft Edge.
• Browsers are fully up to date.
• Multiple users across our team are observing the same behavior.
• Trigger execution appears correct; the discrepancy is only visible in the Monitoring view.
• The issue began after our recent time zone migration.

Based on our investigation, this appears to be either:

• A monitoring UI timestamp display issue, or
• An incorrect time zone conversion being applied within the Synapse monitoring portal.

Could you please assist with the following?

1. Confirm whether this is a known issue related to recent time zone or DST changes.
2. Advise if there are any additional settings that need to be updated.
3. Review the behavior and confirm whether the monitoring timestamps are being displayed correctly.

We have attached screenshots showing the discrepancy between the trigger time and the displayed Run Start time.

Please let us know if you require any additional information, including workspace details, subscription information, or diagnostic logs.