Synexa Holiday Notice
Scheduling and timezone troubleshooting
Resolve timezone, daylight-saving, expired notice and overlap problems.
Updated
If a notice starts or ends at an unexpected time, first check the timezone shown in the app. The shopper's location and computer clock do not determine the schedule you entered.
Verify the timezone and dates
- Check Dashboard → Store timezone or open Settings → IANA timezone. Supported examples include
Asia/Kolkata,Europe/London, andAmerica/New_York. - Open the notice and read the timezone displayed in Schedule.
- Verify both date and time for each populated boundary. Time uses the 24-hour format:
09:00is morning, and21:00is evening. - If you want immediate eligibility, clear the start date and time together. For no automatic expiry, clear both end fields.
- Confirm the end is later than the start, then save.
Daylight-saving changes
Some timezones skip a local time when clocks move forward or repeat one when clocks move back. If the form rejects an ambiguous or nonexistent time, choose an unambiguous time outside that transition. Do not repeatedly change your computer clock to try to fix the notice.
The app stores schedules as fixed UTC instants. Changing IANA timezone later changes the displayed local representation of existing notices, without shifting when they run. If your intended business hours changed, edit the notice's actual dates and times as well.
Check state and overlapping notices
A future start does not make a Draft eligible. The notice must be Published and enabled. It stops being eligible at the exact end time; midnight means the beginning of that date.
Other notices may take the available display positions. Compare priorities, and remember that Free and Starter show one notice while Pro shows up to three. A dismissed selected notice does not promote the next one. The storefront refreshes configuration periodically, so allow a short refresh interval or reload when testing a recent change.
When to contact support
Provide the store timezone, entered start/end values, notice title, visible state, and the actual time of the unexpected result. Avoid sending credentials or customer data.
Related guides
Covers the Phase 1 scheduling behavior reviewed in October 2026.