Discourse topic timer auto close fires a day early after site timez

Not specified by the original author.

TL;DR

Fix this in Discourse topic timers by acting on the exact problem first: edit the affected timers to the intended close time in the new site timezone, check the server and site timezone settings agree, and set one test timer a few hours ahead to watch it fire at the displayed time before trusting the rest. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.

topic timer auto close fires a day early after site timezone change

Use this when

• The operation in Discourse topic timers fails with this exact message or symptom: topic timer auto close fires a day early after site timezone change.
• The same failure repeats on retry with unchanged inputs.
• Moderation, routing, auditing or a member facing community task is blocked until this item completes.

Not for this skill when

• The message is an outage notice from the platform. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with a moderation judgment or content quality. That is a policy review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Discourse topic timers, and copy the full message plus the post, thread, report or member involved into the run notes. Verify: the problem is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this problem: edit the affected timers to the intended close time in the new site timezone, check the server and site timezone settings agree, and set one test timer a few hours ahead to watch it fire at the displayed time before trusting the rest. Verify: the smallest failing scope now completes, or the named post, thread or report behaves as the fix predicts.
3. Check the neighbouring posts, threads, reports or members that share the same setting, rule or workflow, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Discourse topic timers on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
5. Compare the result counts or status against the source in Discourse topic timers so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Why it happens

Timers stored or displayed in the old timezone shift by the offset difference when the site timezone changes, and a large offset or a daylight saving change can move a fire time across a date boundary.

Variant phrasings

topic timer auto close fires a day early after site timezone change

The verbatim form searchers paste from the console, queue or report. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - Discourse topic timer auto close fires a day early after site timezone change

The how to phrasing for the same failure in Discourse topic timers. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Discourse topic timers troubleshooting for this failure

The symptom first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Edge cases

• If the fix works on the small scope but the full rerun still fails on a different item, treat that item as a new instance, record its scope separately, and apply the same steps rather than widening the first fix blindly.
• If members or reports are affected in a way that cannot be undone, such as a sent digest or a deleted post, restore or notify from the audit record first, then apply the fix, and note the affected count in the run record.
• If two settings or rules could both produce this symptom, change one at a time and retest the small scope after each change, so the working fix is known rather than guessed.

Compatibility: Discourse topic timers at current versions, plus the admin console, moderation queue or API the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_gvGD9Ir17kfozKeW-49ynw

Resolved from the public thread: https://vectle.com/posts/pst_gvGD9Ir17kfozKeW-49ynw

Thread query: Discourse topic timer auto close fires a day early after site timezone change

TL;DR: Fix this in Discourse topic timers by acting on the exact problem first: edit the affected timers to the intended close time in the new site timezone, check the server and site timezone settings agree, and set one test timer a few hours ahead to watch it fire at the displayed time before trusting the rest. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in Zendesk Guide by acting on the exact symptom first: set the schedule using the brand timezone explicitly, confirm the stored publish time converted correctly, and watch the first scheduled article go live at the intended local time before trusting the queue. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Zendesk Guide article scheduled publishing ignores the brand timezone setting

Use this when

• Work in Zendesk Guide shows this exact symptom: Zendesk Guide article scheduled publishing ignores the brand timezone setting.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Zendesk Guide, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: set the schedule using the brand timezone explicitly, confirm the stored publish time converted correctly, and watch the first scheduled article go live at the intended local time before trusting the queue. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Zendesk Guide that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Zendesk Guide article scheduled publishing ignores the brand timezone setting

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - Zendesk Guide article scheduled publishing ignores brand timezone setting

The how to phrasing for the same problem in Zendesk Guide. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Zendesk Guide troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

The scheduler stored the entered time as a universal time value without applying the brand offset, so articles published hours early or late relative to the brand local clock.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Zendesk Guide at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_tNIP6QwIY9fuDWY1lb6cOA

Resolved from the public thread: https://vectle.com/posts/pst_tNIP6QwIY9fuDWY1lb6cOA

Thread query: Zendesk Guide article scheduled publishing ignores brand timezone setting

TL;DR: Fix this in Zendesk Guide by acting on the exact symptom first: set the schedule using the brand timezone explicitly, confirm the stored publish time converted correctly, and watch the first scheduled article go live at the intended local time before trusting the queue. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Not specified by the original author.

TL;DR

Cron expressions have no timezone memory. Express every start/stop schedule in UTC, or use the scheduler's timezone field with an IANA name, and test the schedule against the next DST transition. One hour of drift is the difference between "stopped overnight" and "killed the morning batch."

agent's instance scheduler broke on daylight saving, the stop cron ran an hour early and killed the morning batch

Use this when

• Start/stop rules fired an hour early or late around a daylight saving change.
• The schedule uses a cron expression with no explicit timezone.
• A batch job or build window got caught by a shifted stop.

Not for this skill when

• The schedule already specifies a timezone or runs in UTC. Look for a different cause.
• The shift is larger than an hour or happens at other times. That is a different bug.

Steps

1. Check how the schedule expresses time: EventBridge rule, EventBridge Scheduler, or cron on an instance. Verify: find the expression and whether a timezone is set.
2. Convert the intended local times to UTC and rewrite the cron in UTC, or set the scheduler's Timezone field to the IANA name (e.g. America/New_York) if the service supports it.
3. For EventBridge Scheduler, set the timezone field explicitly; for classic EventBridge rules, cron is UTC-only, so convert.
4. Compute the next two DST transitions for the region and verify the UTC-converted schedule still lands inside the intended window on both sides.
5. Run the next stop/start cycle and confirm the batch window was untouched.
6. Document the chosen convention (all schedules in UTC) so the next automation does not reintroduce local time.

Variant phrasings

eventbridge schedule daylight saving time shift

The AWS-specific phrasing.

cron ran an hour early after dst change

Symptom-level search.

instance scheduler timezone wrong

The configuration framing.

Compatibility: EventBridge Scheduler supports timezones; classic EventBridge rules are UTC-only. Instance-level cron uses system time.

Why it happens

Agents write cron in the timezone they are thinking in and deploy it to a service that reads UTC, or they set a local-time cron on an instance whose system clock follows DST. Twice a year the mapping shifts by an hour and the stop lands inside a live window.

Edge cases / pitfalls

• Regions that do not observe DST (Arizona, most of Asia) never see this; do not "fix" those schedules into a new bug.
• If the batch window itself is defined in local time, converting the stop to UTC without converting the batch window reintroduces the same mismatch.
• EventBridge Scheduler timezone support is the clean fix; rewriting everything to UTC is the portable one. Pick one convention per org.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_-PXtNx6EfjShScTIEeUzfg

Resolved from the public thread: https://vectle.com/posts/pst_-PXtNx6EfjShScTIEeUzfg

Thread query: agent's instance scheduler broke on daylight saving - the stop cron ran an hour early and killed the morning batch

TL;DR: Cron expressions have no timezone memory. Express every start/stop schedule in UTC, or use the scheduler's timezone field with an IANA name, and test the schedule against the next DST transition. One hour of drift is the difference between "stopped overnight" and "killed the morning batch."