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

Venkata Ramana Nagulapati 0 Reputation points
2026-11-03T17:25:24.9866667+00:00

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.

time zone mismatch

Azure Monitor
Azure Monitor

An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Allan Solomon Mejia 10,640 Reputation points
    2026-11-04T02:43:32.45+00:00

    Hello @Venkata Ramana Nagulapati

    The one-hour difference matches the Alberta transition from the former seasonal Mountain Time rules to permanent UTC−06:00 on November 1, 2026. A timestamp of 15:00Z should now display as 9:00 AM in Alberta; software still applying the previous winter offset of UTC−07:00 will display it as 8:00 AM. Alberta now requires the new (UTC−06:00) Mountain Time (Alberta) time zone.

    Because the pipelines execute at the intended time and only the Monitor view is one hour behind, do not modify the working trigger schedules based solely on the displayed Run Start value. Synapse trigger-related timestamps are stored and returned in UTC using ISO 8601, while monitoring interfaces convert timestamps for display.

    To confirm whether this is strictly a display-conversion issue:

    1. Record the affected pipeline RunId.
    2. Retrieve that run through the Synapse pipeline-run API and inspect runStart, runEnd, and durationInMs.
    3. If diagnostic logging is enabled, compare it with SynapseIntegrationPipelineRuns.Start and End, which Microsoft documents as UTC fields.
    4. For a 9:00 AM Alberta execution, verify that the raw start time is approximately 15:00Z.

    If the raw value is 15:00Z but Synapse Studio displays 8:00 AM, the pipeline metadata is correct, and the defect is in the Monitor UI’s local-time conversion. As a temporary viewing workaround, select UTC in the monitoring time-zone selector, or select a fixed UTC−06:00 zone such as Saskatchewan if that option is available. Microsoft documents that pipeline monitoring displays browser-local time by default and allows the display time zone to be changed. Visually monitor pipelines

    Also confirm that each workstation:

    • Has the applicable Windows time-zone update installed.
    • Uses (UTC−06:00) Mountain Time (Alberta) rather than the older Mountain Time (US & Canada) entry.
    • Has restarted the browser after the Windows time zone change.

    Outdated devices or devices still using the former zone can display the wrong local time after November 1.

    I cannot find verified official documentation confirming a Synapse-specific known issue for this Alberta transition. If the raw UTC value is correct and multiple fully updated workstations still show 8:00 AM, submit an Azure support request with the workspace ID, pipeline RunIds, raw UTC timestamps, screenshots, selected monitoring time zone, browser versions, and Windows build numbers. That evidence isolates the issue to Synapse Studio’s display conversion rather than pipeline scheduling.

    References:

    Help make this community better for everyone: If this answer helped or resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution. Thank you.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.