The short answer
A schedule change does pause delivery briefly and can soften reporting for a few hours
Yes, a mid-cycle schedule change does create a visible gap. Delivery can pause for anywhere from under an hour to a few hours while the change is applied, and that day's data can lose a few hours' worth (a negligible amount). If the change also triggers editorial review of new ads, the gap can stretch longer while Hugo works with the platform toward approval or an appeal.
What happens right after a schedule change is submitted
When a Compass agent asks for a mid-cycle strategy change, that update has to push out to the ad platforms before it takes effect. That push isn't instant. Delivery can pause for a stretch while the change is applied and deployed, and the length of that pause depends on the platform itself. Some platforms pick up changes quickly, others take longer to process them, so the pause can run from under an hour to a few hours.
During that window, reporting can show a soft spot too. That day's numbers might be missing a few hours of activity because delivery wasn't running the whole time. Hugo treats this as a small, expected cost of making a change, not a sign that something is broken. The data comes back to normal once delivery resumes.
When the gap runs longer than expected
The short pause described above is the typical case. But if the schedule change involves new ads, it can trigger editorial review on the platform side. That review process is outside Hugo's control on timing, and it can make performance look like a longer outage while the platform works through approval.
Sometimes an ad gets disapproved during that review. When that happens, Hugo files an appeal and works directly with the platform toward a resolution. This is the scenario most agents actually mean when they ask why part of a run ended early and had to get extended. It's not a permanent loss of delivery, it's a review cycle playing out, and Hugo stays on it until the ad is cleared or the issue is resolved.
Does delivery actually stop when a schedule change is made?
Yes. When the change pushes out to the ad platforms, delivery can stop while it's applied and deployed. How long depends on how fast that platform ingests the update.
Hugo, as of 2026-08-13: delivery can stop while the change is made and deployed, anywhere from less than an hour to a few hours depending on the platform's ingestion.
Will this show up as missing data in reporting?
There can be a small gap, but it's minor. A mid-cycle schedule change can cost a few hours of that day's reporting data, and Hugo treats that loss as negligible in the bigger picture.
Hugo, as of 2026-08-13: a mid-cycle schedule change can cost up to a few hours of that day's reporting data, and the loss is negligible.
Why would the gap last longer than a few hours?
If the schedule change involves new ads, it can kick off editorial review with the platform. That review can make performance look off for a longer stretch, especially if an ad gets disapproved and needs an appeal.
Hugo, as of 2026-08-13: if a schedule change kicks off editorial review of new ads, performance can look like an outage while waiting on the platform's review and approval, and ads sometimes get disapproved, requiring Hugo to file an appeal and work with the platform toward resolution.