Claude Cowork cloud scheduled-task chain holding a 7am Eastern cron across US DST (11 UTC EDT, 12 UTC EST); ask CoWork for your task's trigger ID

Claude Cowork DST trigger chain

This prompt maintains itself. Each firing updates one recurring task's cron expression, then schedules the next firing at the following US daylight-saving transition. Do not edit it except to set the configuration values below.

Configuration

• TRIGGER_ID — trig_xxxxxxxxxxxxxxxxxxxxxx (the Claude Cowork cloud scheduled task to keep on time)
• EST_CRON — 0 12 * * *
• EDT_CRON — 0 11 * * *

Do everything below now, silently: no confirmation prompts, and no message to the user.

Step 0: Determine where you are

Let Y be the current year. If the current month is March, US clocks have just sprung forward, so PHASE is SPRING. If November, they have just fallen back, so PHASE is FALL. If neither, stop and send an email notification reporting the unexpected firing date; do not modify or create anything.

Step 1: Verify, then update the recurring task

Look up TRIGGER_ID. If it does not exist, stop and send an email notification reporting that the trigger was not found; do not update anything.

Otherwise call update_trigger with trigger_id set to TRIGGER_ID and cron_expression set to EDT_CRON if PHASE is SPRING, or EST_CRON if PHASE is FALL. This holds the task at 7:00am local Eastern year-round: EDT is UTC-4, so 11:00 UTC; EST is UTC-5, so 12:00 UTC.

Step 2: Schedule the next link in the chain

If PHASE is SPRING, the next transition is the first Sunday in November of year Y, and the new trigger is named DST: fall back (Y). If PHASE is FALL, the next transition is the second Sunday in March of year Y+1, and the new trigger is named DST: spring forward (Y+1). Use the literal year number in the name.

Call create_trigger with:

• name: as determined above
• run_once_at: 08:00:00Z on that date
• initiation: own_followup
• notifications: {"push": false, "email": false}
• prompt: this entire prompt, character for character, exactly as you received it. Add nothing, remove nothing, alter nothing. Every value it needs is derived at run time, so there is nothing to substitute.

If create_trigger fails, send an email notification describing the failure. Otherwise the chain ends here silently, and the task will drift an hour off at the next transition.