Skip to main content

Setting your display timezone

Your display timezone is the zone Studio uses to show dates and times, such as when a workflow was created, when a deployment ran, or when a log entry was written. Set it once and it follows you across sessions and devices. Change it when you work across regions, or when the times you see do not match your local clock.

Before you begin​

The setting belongs to your own account. It changes only what you see, not what your teammates see.

Set your timezone from your preferences​

  1. Open Settings > Account > Profile > Preferences.
  2. Under Display Timezone, open the timezone list and choose your zone.
  3. Select Save.

To go back to the zone your browser reports, select Reset to browser zone under the list, then select Save. This link appears only while the selected zone differs from your browser's. To discard a change you have not saved, select Cancel.

Change your timezone from the application toolbar​

While you work in an application, the bottom toolbar shows a clock button with a short label for your current zone, such as IST or EDT. Use it when you want to switch zones without leaving your work.

  1. Select the clock button in the bottom toolbar.
  2. Choose a zone from the list. The change is saved as soon as you pick it, so there is no Save step.

To use your browser's zone again, select Reset to browser zone in the same popover. Hover over the clock button to see the full zone name, its UTC offset, and its identifier.

What the setting changes​

Dates and times across Studio are shown in your display timezone. Hover over a timestamp to see the full value with its zone spelled out, for example 2026-08-05 12:36:39 IST (UTC+05:30).

Some timestamps look different after the 1.2.7 upgrade. They now reflect your selected timezone, so a time you remember from before may have shifted by your offset from UTC.

What the setting does not change​

  • Schedule activity timezones. A schedule runs in the timezone set on the Schedule activity itself, not in your display timezone. Schedules with no timezone run in UTC. See Schedule for how to set a schedule's timezone.
  • Cron expressions. The cron expression shown for a schedule is the one the backend runs, and it is not shifted into your zone.
  • Other people's view. A teammate sees times in their own display timezone, not yours.

On a deployed workflow's schedule details, Next execution, Starts on and Ends On appear in the schedule's own zone by default. When that differs from your display timezone, a Show times in switch appears. Choose Schedule for the schedule's zone or Mine for your display timezone.

What you see before you choose a zone​

Until you save a zone, Studio uses the timezone your browser reports on each device. Two devices in different regions can therefore show different times until you pick a zone on one of them. Once you save a zone it applies on every device you sign in from, and a browser's zone no longer overrides it.

If a saved zone is empty or not recognized, Studio falls back to your browser's zone.

How you know it worked​

  • From the preferences page, the message Preference saved successfully appears and the Save button is disabled again.
  • From the toolbar, the clock button shows a spinner while saving, and its label changes to the new zone.
  • Timestamps across Studio update to the new zone, and hovering one shows the new zone in its detail.

When it does not work​

SymptomCauseWhat to do
Timezone not recognised, so it was not savedThe selected zone is not one the browser can read.Choose a different zone from the list, then save again.
Couldn't save timezone; kept the current oneThe toolbar could not save your choice, so your previous zone stays in effect.Try again.
Couldn't save timezone; sign in and try againYour session has no signed-in user.Sign in again, then retry.
Something went wrong! Please login againThe preferences page could not identify your account.Sign in again, then retry.
A time still looks wrong after the upgradeThe browser may still be running the previous version.Do a hard reload and clear the browser cache, as the 1.2.7 release notes advise.

Next steps​