Skip to content
C CountdownFlow Help Center Sign in

Understanding feature limits and usage

Learn to identify and resolve issues when campaigns hit feature or usage thresholds.

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.

Distinguishing features from usage volume

Feature switches enable or disable capabilities such as branding, API access, or animated GIFs, while quantity limits govern usage volume, such as template storage or history access.

A limit of zero denotes a hard restriction, not unlimited access. A blank quota may indicate that no additional limit applies, depending on plan settings. Always reference the specific labels provided on the screen rather than assuming the meaning of empty values.

Billing and usage screen showing the example workspace’s plan information
Use your workspace’s actual plan and allowances as the source of truth. Any plan or subscription shown here is demonstration data, not a purchase offer. View full-size screenshot (opens in a new tab)

Why campaigns become restricted

Plan downgrades, subscription changes, or updates to reseller entitlements may render campaigns incompatible with the current workspace's capabilities. These restrictions are enforced server-side; saved templates do not exempt campaigns from runtime feature requirements.

Resolving restricted campaigns

  1. 1Consult the plan notice to identify the specific incompatible settings.
  2. 2Modify or remove restricted settings section by section, such as switching to a basic composition, clearing disabled button text, or selecting a supported format.
  3. 3Save each section as you repair it. You may maintain some violations while addressing others, provided you do not introduce additional restricted settings.
  4. 4Resolve all violations before previewing, publishing, or deploying, or have the owner upgrade to a plan that supports your requirements.

Understanding history versus volume limits

History windows restrict access to older records without necessarily purging them. Delivery usage allowances count requests reaching the service, rather than simply tracking the number of newsletters sent.

Factors like proxy caching, automated requests, and repeated fetches can cause discrepancies between service activity and email provider statistics. Refer to the actual usage panel and metric definitions instead of estimating consumption based solely on send volume.

Related articles