Skip to content
C CountdownFlow Help Center Sign in

Troubleshooting timer and scheduling issues

Isolate problems with campaign deadlines and status without disrupting live offers.

2 min read

Screenshots use fictional demo data. Your controls may differ by plan, role, or environment. Use the values generated in your own workspace.

Verifying saved campaign settings

  1. 1Check the workspace, campaign name, and publication status.
  2. 2Confirm the timer type; daily or recurring rules repeat, while fixed-date rules do not.
  3. 3Review the campaign timezone and the saved deadline or duration without incorrectly comparing local times.
  4. 4Verify any optional start dates, hard stops, enabled overrides, phases, and extensions.
  5. 5Check for plan warnings before attributing restricted delivery to a clock failure.
Fixed-date campaign editor showing timing configuration
The campaign form groups timing and expiration controls separately from the visual designer. View full-size screenshot (opens in a new tab)

Debugging timer resets

For evergreen campaigns, verify identity before adjusting the duration. A new device, a different browser, cleared storage, or a missing 'vid' parameter can trigger a new anonymous identity. Additionally, a missing or improperly replaced provider tag can disrupt recipient matching. Test again using one stable opaque ID in both the image and link; the request should return the same effective deadline.

Investigating channel inconsistencies

Ensure that your channels reference the same campaign and recipient context. Distinguish between a live website snapshot and a cached email image or previously loaded GIF. If the server snapshot is accurate but the inbox result differs, caching is a more likely cause than a timezone discrepancy.

Understanding early expiry

  • The fixed deadline may have already passed in the selected timezone.
  • A recurring schedule may currently be outside of its defined weekdays or hours.
  • A future start date may keep the campaign in a waiting state.
  • An evergreen hard stop may have shortened the recipient's window.
  • A paused, unpublished, or plan-restricted campaign may be unavailable even if timing fields appear valid.

Data to include for support

Provide the campaign ID or name, timezone, expected result, actual result, affected channel, and a screenshot that excludes private recipient data. Describe whether the issue persists with a fresh request and a stable test identity. Never share your API key or signing secret.

Related articles