Which time zone do services use?

[daniel]

I have a service where Europe/Oslo is set as the default time zone. However, when I trigger the service from devtools for services (from Bergen, Norway, in case that matters) Now gives me UTC.

Is this intensional?
Am I doing something wrong?
Which time zone will be used when the service is triggered from an app or a schedule if I dont use overwrite timezone?

[daniel]

[kristian]

Hi!

The Services run in the time zone that is
a) Configured in the Service Settings (default: Europe/Oslo)
b)…or the one configured in “Run Service” action node, or on the Service Schedule (may override the Europe/Oslo default).
Dev Tools use the time zone given on the Service Settings.

In your code, a few things to note:

1. The now variable is a pure JSON date (e.g. 2026-08-24T13:08:14.430Z). Running “toLocaleString()” on it just turns it into a string-date. I believe the same happens when you apply it to the “hours” variable.
2. The Date object you use does not store or hold time-zone. If you choose to use that lib, you can set the time zone on that variable, e.g.

const date = new Date();

const osloTime = date.toLocaleString("en-GB", {
    timeZone: "Europe/Oslo"
});

However, we do not set time zone on Date() type variables.

3. If you instead use the moment() library (that may be added from the left side in the function editor) it knows your timezone. return moment().hours() returns “15” if it is 15:00 in Oslo when the Service is triggered form Devtools. Also, if you use built-in value processors, or conditions such as ServiceVariables.Now.Hours >= 15 there is “moment()-treatment” behind the scenes taking the time zone into account.

I just testet console logging Service Variables.Current Timestamp.Hour, and it prints the correct “Oslo-hour”:

Hope this helps!

[daniel]

This works, thanks for the help!

Feature request: Set time zone on Date() type variables