Timezones

Every cron job has its own timezone. QuzenixCron interprets the cron expression in that zone, so your schedule stays consistent even when daylight saving time shifts.

Default: UTC

If you don't set a timezone, it defaults to UTC. That's the safest choice for systems that span multiple zones — no DST, server-friendly, and your logs stay consistent.

Timezone Format

Use the IANA timezone format (Continent/City). Some common ones:

Asia/Jakarta       — WIB (UTC+7)
Asia/Makassar      — WITA (UTC+8)
Asia/Jayapura      — WIT (UTC+9)
Asia/Singapore
Asia/Tokyo
Europe/London
America/New_York
Pacific/Auckland

Full list: IANA tz database.

Example

Want a job to run every day at 8 AM Jakarta time? Set:

Schedule: 0 8 * * *
Timezone: Asia/Jakarta

The job will fire at exactly 08:00 WIB every day, no matter where your server is hosted.

DST is handled automatically
For zones that observe DST (like Europe/London or America/New_York), QuzenixCron follows the zone's rules automatically. A job scheduled for "9 AM" will always fire at 9 AM local time, even when the UTC offset shifts by an hour.
Indonesia has no DST
If your users are all in Indonesia, you don't need to worry — WIB is always UTC+7. But if you're building for a global audience, watch out: America/Phoenix doesn't observe DST while America/Los_Angeles does.

Checking the Next Run Times

On the job detail page, there's an Upcoming runs section that shows the next 5 scheduled times as absolute timestamps. Use it to confirm your schedule looks right before you rely on it in production.

PreviousAuthenticationNext Retries & Failures