AJO quiet hours queued a message until the next day

A customer should receive a push when quiet hours end at 8 AM. Instead it arrives the following morning. An Experience League report describes that gap. The thread does not prove a product defect or a universal workaround; it gives operators a useful failure case to reproduce.

Reconstruct the calendar, not just the rule label

Adobe’s quiet-hours guide says an overnight weekly period belongs to the day it starts. Draw every selected weekday across midnight in the rule’s configured time zone. Check whether the profile uses a local time-zone field and whether that field is populated. A Tuesday 4 AM arrival may be covered by Monday’s period, depending on the schedule.

Trace one profile from action to send

Record the profile’s journey entry, push action arrival, rule-set version, queue state and actual delivery timestamp. Include time-zone offsets on every timestamp. Adobe says rule updates may take up to 12 hours to reach actions already using the rule; changing a rule and immediately retesting can confuse the diagnosis.

Reproduce before widening a fix

Use a controlled profile at the overnight boundary and compare the expected release time with the actual one. If the documented period calculation still does not explain the delay, send Adobe Support the rule configuration and event timeline. Splitting an overnight period without a controlled test can create a new gap or discard behavior.

Adovo’s view

A send window is part of the customer promise. If the team cannot predict when a queued message leaves, the journey is not ready to scale. Make time-zone and boundary tests a release condition.