Skip to content
CountdownFlow Help Sign in

Feature limits, usage and restricted campaigns

Understand zero allowances, quota warnings and what to do after a plan change.

2 min read

Screenshots show the real application in an isolated demo environment with fictional example data. Setup notices and controls may differ by environment, plan and role. Click an image to view it full-size, and always use the values generated in your own workspace.

Features and quantities are different

A feature switch controls whether a capability is allowed, such as animated GIFs, saved templates, branding or API access. A quantity controls how much is available, such as eligible shared templates or accessible history.

Zero is a blocking allowance, not “unlimited.” A blank quota can mean no additional limit for that quota where the plan settings define it that way. Do not assume every displayed blank or dash has the same meaning; follow the allowance labels on the screen.

Billing and usage screen showing the example workspace’s plan information
In the application 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 a previously working campaign becomes restricted

Downgrades, subscription status changes or revised reseller entitlements may leave a campaign using features its workspace no longer has. Restrictions are enforced on the server, not only by disabling a button in the editor. A saved template is not an exemption for an unsupported runtime feature.

Repair a restricted campaign

  1. 1Read the plan notice for the exact incompatible settings.
  2. 2Remove or reduce those settings one section at a time. For example, use a supported basic composition, clear disabled button copy or choose an allowed format.
  3. 3Save each repaired section. You may keep an existing violation unchanged while fixing another, but cannot add or worsen a restricted setting.
  4. 4Resolve all remaining violations before relying on preview, publishing or public delivery. Alternatively, have the owner choose a plan with the needed capabilities.

History and delivery usage

A history window limits accessible reporting history without necessarily deleting older records. An image/delivery usage allowance concerns requests that reach the service, not simply the number of newsletters you sent.

Proxy caching, repeated fetches and automated requests can make service activity differ from your email provider’s totals. Review the actual usage panel and metric labels rather than calculating allowance consumption from send volume alone.

Related articles

Browse templates and reuse saved designsUnderstand the built-in library, plan-limited choices and why existing campaign designs do not change automatically. Filter reports and export available dataCreate a useful reporting workflow and understand plan-based history limits. Plans, checkout, billing portal and cancellationFind your actual allowances, change billing safely and understand the difference between direct and agency-managed access. Explain and troubleshoot client plan accessUnderstand effective entitlements, agency-managed billing and changes to client allowances.