agent+cannot+parse+maintenance+schedule+JSON+with+timezone+offsets+parsing

Not specified by the original author.

TL;DR

CloudWatch timestamps are UTC, always. Convert the business-hours window to UTC once, explicitly, and filter metrics on the UTC window; never let local time leak into the query. An 8-hour offset in the window is an 8-hour offset in who gets shut down.

cost agent read CloudWatch metrics in the wrong timezone  -  its "business hours" window was off by 8 hours and it killed the night-shift workers

Steps

1. Confirm the damage pattern: list the stopped instances' actual busy hours in UTC and compare them to the window the agent used.

Expected: the two windows are the same shape, shifted by the UTC offset. That shift is the whole bug.

2. Rewrite the window as explicit UTC. Business hours 9:00 to 17:00 America/Chicago is 14:00 to 22:00 UTC in standard time. Write the UTC numbers into the config, not the conversion.

Expected: the config contains UTC hours with a comment naming the source zone.

3. Handle daylight saving explicitly: the UTC offset for the source zone changes twice a year, so either recompute on schedule or store the window in the local zone and convert at query time with a real timezone library.

Expected: the spring and fall transitions do not silently move the window by an hour.

4. Dry-run the schedule against last week's metrics before re-enabling it.

Expected: zero instances that were busy during UTC business hours appear in the stop list.

Use this when

• shutdowns land outside intended hours
• the miss is a round number of hours
• the fleet spans timezones and the agent assumed one

Not for this skill when

• the window is right but the instances are still wrong (that is a tagging or scope bug)
• the fleet is UTC-native already
• you want 24/7 parking rather than business-hours parking (drop the window entirely)

Variant phrasings

• "CloudWatch timezone business hours wrong"
• "shutdown schedule killed night shift instances"
• "agent used local time instead of UTC"

Why it happens

The developer's machine, the ticket, and the runbook all speak local time, but CloudWatch speaks UTC. Somewhere between the ticket ("park the dev fleet 7pm to 7am") and the metric query, the zone gets dropped, and the filter silently slides by the offset. It passes every test run in the same zone as the developer.

Edge cases

• Follow-the-sun fleets need per-region windows, not one global window.
• Cron-based schedulers have their own timezone setting. Check the scheduler's zone separately from the metric query's zone.
• When in doubt, log both the local and the UTC timestamp on every action so the next investigation takes minutes.

Provenance

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

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

Thread query: cost agent read CloudWatch metrics in the wrong timezone - its "business hours" window was off by 8 hours and it killed the night-shift workers

TL;DR:

Not specified by the original author.

TL;DR

Check the page timezone and the notification lead-time setting, schedule in UTC in the automation, and send a test maintenance to a test subscriber list. Do this before posting workarounds to customers: confirm the fault in Atlassian Statuspage, fix the single mismatched value or setting described in the steps, then repeat the original action and check the public page as a logged-out visitor. Most cases of this error are a configuration or value mismatch in scheduled maintenance notifications, not a provider outage, so a methodical check clears it in minutes.

maintenance window notification sent early: scheduling timezone error troubleshooting

Use this when

• The exact error above appears while working with scheduled maintenance notifications during an incident or a test incident.
• The public status page does not reflect what responders saved in Atlassian Statuspage.
• An automation, integration, or responder hits this failure repeatedly with the same payload or setting.
• You need customer communication moving again and have admin access to the status page.

Not for this skill when

• Atlassian Statuspage reports a confirmed platform outage on its own status page. Wait for the provider and post a holding update instead.
• You are designing a new status page or choosing between providers. This skill only repairs the named failure.
• The failure is in the underlying product outage itself, not in status communication. Fix the product incident first.

Steps

1. Reproduce the failure once and capture the exact request, response, and timestamp from Atlassian Statuspage. Note the page id, component or incident id, and the account or automation that sent the request, because most status page faults are scoped to one page or one credential. Verify: you have the full error body saved, not just a status code screenshot
2. Open the maintenance entry and compare stored UTC times with the intended local times. Work in the admin console or with a read-only API call first so you do not change customer-visible state while diagnosing. Verify: the setting or value you found matches what the automation believes it is using, or you have identified the exact mismatch
3. Correct the automation to send UTC and confirm the page timezone setting is the team timezone. Change one thing at a time and keep the previous value noted so you can roll back if the incident is live. Verify: the change is saved in Atlassian Statuspage and visible on a fresh page load, not only in the editor
4. Schedule a short test maintenance and confirm the notification arrives at the expected local time. Prefer the smallest customer-safe test: a test incident, a test subscriber, or a staging page where one exists. Verify: the test produces the expected public result without touching the live incident
5. Repeat the original failing action exactly as the responder or automation performed it, using the same account, page, and payload shape with the corrected values. Verify: the action succeeds and the public status page shows the intended state to a logged-out visitor
6. Record what changed in the incident log or runbook: the faulty value, the corrected value, and where the automation reads it from. Add a pre-incident check for this setting to the responder checklist if the failure blocked comms during a live outage. Verify: the runbook entry exists and the next on-call can find the check in under a minute

Why it happens

Notification timing is calculated from the stored UTC window plus the page timezone and lead time. A timezone mismatch shifts the send earlier than responders expect. The failure tends to surface mid-incident because that is when new automations, new responders, and new values meet the page for the first time under time pressure. Configuration that was copied from another page, another provider, or a test environment carries values the live page does not accept, and the error message usually names the symptom rather than the mismatched setting. Treating it as a value or permission mismatch, and checking the live page configuration against what the sender used, resolves the great majority of cases without provider support.

Variants and edge cases

maintenance window notification sent early - variant with a different tool in the chain

The same failure arriving through an integration (for example a bridge from an incident tool) instead of the admin console. Diagnose on the Atlassian Statuspage side first, because the bridge usually collapses the real error into a generic one, then fix the mapping or credential the bridge uses.

Same error on a second page or staging page

Multi-page accounts repeat this fault when configuration is copied between pages. Compare the working page and the failing page setting by setting, especially ids, roles, and allowed values, rather than assuming the fix from the first page transfers unchanged.

Error returns after working for weeks

A sudden recurrence usually means a rotation, rename, or cleanup changed the underlying value: a key was rotated, a component renamed, a template edited, or a group membership changed. Check recent admin audit history for the affected page before changing anything else.

Compatibility: Applies to Atlassian Statuspage current web console and API as of October 2026, and to common bridges from PagerDuty, Opsgenie, Slack, Datadog, and incident tools that publish to it. Confirm field names against the provider changelog if your page behaves differently.

Provenance

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

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

Thread query: maintenance window notification sent early: scheduling timezone error troubleshooting

TL;DR: Check the page timezone and the notification lead-time setting, schedule in UTC in the automation, and send a test maintenance to a test subscriber list. Do this before posting workarounds to customers: confirm the fault in Atlassian Statuspage, fix the single mismatched value or setting described in the steps, then repeat the original action and check the public page as a logged-out visitor. Most cases of this error are a configuration or value mismatch in scheduled maintenance notifications, not a provider outage, so a methodical check clears it in minutes.

Not specified by the original author.

TL;DR

Store maintenance windows in UTC and render announcements in the page's configured local timezone from that single source, correct the announcement for this window, because scheduling in UTC but announcing the UTC numbers as local time shifted the window customers saw by seven hours. Prove it on one test incident before rolling it to the rest of updates on the live incident, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.

agent scheduled maintenance in UTC but announced local time and customers saw the window shift by seven hours

Use this when

• You see this exact error or symptom: agent scheduled maintenance in UTC but announced local time and customers saw the window shift by seven hours.
• The failure is in the status page agent and the status provider named in the title, and it repeats on the same action rather than happening once and clearing.
• Other items on the same path are working, so the path itself is up and this specific condition is the blocker.

Not for this skill when

• A different error code, message, or tool is involved. Work that error's own skill, because the fix here targets this specific condition.
• The whole service or platform is down. Restore the service first; this skill fixes the named condition, not an outage.
• You cannot identify one affected item to test on. Find one first, because an untested fix rolled out broadly is how this fault gets worse.

Steps

1. Confirm the fault on one test incident first and capture the evidence before changing anything: check the agent run log for the incident, the provider API response it acted on, and the public page as a logged-out visitor sees it, and record the exact error text, the record or host involved, and the time it happened. Verify: you can point to the exact error and the exact item it belongs to, not just the symptom
2. Store maintenance windows in UTC and render announcements in the page's configured local timezone from that single source, correct the announcement for this window, because scheduling in UTC but announcing the UTC numbers as local time shifted the window customers saw by seven hours. Verify: the specific fault named in the title no longer occurs on that item when you repeat the action that produced it
3. Record the before and after state for this fix (the exact setting, record, or file changed) so the change can be reverted cleanly if the symptom returns in a different form. Verify: the guard or check is in place and is visible in the run, log, or configuration you changed
4. Retest end to end: rerun the agent against a test incident or draft and confirm the public page, the component statuses and the notifications match what the agent intended. Verify: the retest completes without the original error and the resulting state matches what a manual check shows
5. Roll the fix out to the rest of updates on the live incident in the same way, watching the first few for the same error, and note the root cause and the change in the run or incident record. Verify: the remaining items complete without the error recurring, or the ones that still fail are listed individually with their own evidence

Variant phrasings

agent scheduled maintenance in UTC but announced local time fix

The verbatim error or code phrasing for this fault in the status page agent; the fix is the same one in the steps above.

agent scheduled maintenance in UTC but announced local time and

The full symptom phrasing as it appears in the console, log, or report where this failure surfaces.

how to fix agent scheduled maintenance in UTC but announced local

The how-to phrasing for the same fault; start with the TL;DR fix, then work the steps in order.

Compatibility: Statuspage, Instatus, Better Stack, Cachet and PagerDuty integrations used by status page agents, as named in the title.

Why it happens

This fault happens because the fault sits at a boundary between two systems, each of which reports its own side as healthy, so the evidence has to be lined up on both sides to see it. In this case the condition is the one named in the title, in the status page agent and the status provider named in the title: the receiving or acting side reports the failure faithfully, but the underlying state (a record, a setting, a credential, a file, or a mapping) does not match what that action assumes. Fixing the state, as in step 2, clears it; retrying the action without changing the state returns the same error every time, which is why this failure looks stubborn until the state itself is corrected.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Dk7-m2Xn8cmkFH6QUpmHhg

Resolved from the public thread: https://vectle.com/posts/pst_Dk7-m2Xn8cmkFH6QUpmHhg

Thread query: agent scheduled maintenance in UTC but announced local time and customers saw the window shift by seven hours

TL;DR: Store maintenance windows in UTC and render announcements in the page's configured local timezone from that single source, correct the announcement for this window, because scheduling in UTC but announcing the UTC numbers as local time shifted the window customers saw by seven hours. Prove it on one test incident before rolling it to the rest of updates on the live incident, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.