A Feature or Action Is Unavailable

Sometimes the problem is not a setting you got wrong. A part of A vs B can be switched off, your organization can be put on hold, or you can hit a limit that comes with your plan. This page covers each of those, what you will see, and what to do next.

A feature has disappeared

Occasionally A vs B switches a whole feature off. Sometimes that is for everyone at once, usually while we deal with a problem and want to stop it spreading. Sometimes it is for a single organization, for example while we look into something on that account.

What you will see

• The feature itself is gone from the left sidebar. There is no upgrade prompt, because this has nothing to do with your plan. This is the main signal that something has been switched off.
• A notice may also appear across the top of your dashboard. A vs B turns this on when it is useful to explain what's happening, for example during an incident. When it does appear, it names the feature and tells you which of the two situations below you are in. It goes away by itself as soon as the feature comes back, so you never have to dismiss it or wonder whether it is still true.
• Opening one of its pages by its address shows a "page not found" screen.
• Requests to the API or the CLI for that feature answer with the message: "This feature is currently unavailable. Contact support if you have questions."
• For the features that run on your own website (web experiments, feature flags, and the e-commerce features), the change reaches your live site too, so those experiments and flags stop being served to visitors. If it was switched off for your organization alone, that usually takes a few minutes. If it was paused across all of A vs B, your dashboard and the API reflect it immediately, but the change reaching every affected organization's live site rolls out gradually rather than all at once, so it can take longer than a few minutes. The rest of the features only stop working inside A vs B.

What to do

If a notice is showing at the top of your dashboard, read it first. It will already tell you which of the two situations below you are in. If there is no notice, contact support and mention which feature is missing, and they will tell you:

• Switched off for your organization. We will tell you why and what happens next.
• Paused on our side. There is nothing to do. Access comes back on its own once the work is finished, and status.avsb.cloud is the quickest way to follow along.

Either way, nothing on your side is broken, and nothing you built is deleted: your experiments, flags, metrics, and settings stay exactly where they were. When the feature is switched back on, everything comes back as it was, and the change reaches your live site again on the same timeline described above.

Your organization is suspended

A suspended organization is one A vs B has put on hold. A suspension is always applied by a person at A vs B and always has a recorded reason, so support can tell you exactly why. It applies everywhere, not only in the dashboard.

What you will see

The message "This organization is suspended. Contact support to restore access." comes back from the dashboard, from the public API, from your service tokens and personal access tokens, from the avsb command line tool, and from the visual editor. No token and no CLI session is a way around a suspension.

A suspension also reaches your own website: the A vs B snippet stops doing anything at all, so no experiments or flags are served to your visitors while the suspension lasts. Nothing is deleted, and everything resumes once access is restored.

What still works

So that you can put things right, these keep working while an organization is suspended:

• Billing. You can still open your billing pages, update your card, settle what is owed, and change your plan.
• Your own data. Data export and deletion requests still go through, because those are your rights and are never held back.

What to do

Contact support and ask what the suspension is for. If it is a payment problem, start on the Billing tab: update your card and the outstanding payment is retried automatically.

You have reached a limit on your plan

A vs B can cap how many projects you run and how many people are in your organization. Today, no standard plan does this: Free and every paid tier both leave projects and team members unlimited by default. A limit only exists if A vs B has set one specifically for your organization, as part of a custom, negotiated agreement. Whatever the source, the limit applies at the moment you try to add something new.

What you will see

Creating the project or adding the member fails, and A vs B tells you: "You have reached your plan's limit. Upgrade to add more."

What to do

• Contact support. Because a project or member cap is a custom limit set for your organization rather than part of the standard plan ladder, support is who can raise or remove it.
• Archive a project you no longer need. Archived projects do not count towards a project limit, so archiving one frees a slot straight away. Your archived project and its history stay in A vs B.

Delivery to your site is paused

Every organization gets 10,000 tested visitors a month for free. Past that, delivery to your site pauses when there are no billing details on file that we can charge. It also pauses when a spend limit you set has been reached, or when a card payment has been open and unpaid for 14 days.

What you will see

• A full-width notice at the top of every page, the experiment builder included, naming the reason. Owners and Admins also get a button to the Billing tab. Other members are asked to get one of them to act.
• Anything that would put new content live is blocked. You cannot start or resume an experiment, or start a feature flag. You also cannot publish changes to a running experiment, or to a flag where it is running. The message names what to fix:
  • "Delivery is paused for your organization until billing details are added. Add them under Settings, Billing (/settings?tab=billing)."
  • "Delivery is paused for your organization until the spend limit is raised or next month starts. Change it under Settings, Billing (/settings?tab=billing)."
  • "Delivery is paused for your organization until the card on file is updated. Update it under Settings, Billing (/settings?tab=billing)."
• The same message comes back from the public API, your API tokens, and the avsb command line tool, so a token is not a way around it.

What is paused

• Visitors see your original pages, not the experiment.
• Feature flags return their default values.
• New events are not recorded.

What still works

• Your dashboard: results, reports, exports and settings all keep working.
• Everything you have built: experiments, flags, projects and your team all stay exactly as they are.
• Saving drafts, and publishing changes to a paused experiment.

What to do

Open the Billing tab and fix whichever caused the pause: add billing details, raise your spend limit, or update the card on file. Only Owners and Admins can open it, so if you are not one, ask one of them. Delivery resumes within about a minute, or on its own at the start of the next month when the free 10,000 resets.

A vs B is down for maintenance

Occasionally A vs B is taken offline on purpose for a short planned maintenance window.

What you will see

• In a browser: a Down for maintenance page, sometimes with a short note from us about when we expect to be back.
• From the API or the CLI: an error saying the service is temporarily down for maintenance, along with how long to wait before trying again.

What to do

Wait it out and try again. There is nothing to fix on your side, and it is worth knowing that a maintenance window only pauses A vs B itself: the experiments and flags you have already published keep running on your own website, and visitor data keeps being collected while we work. Check status.avsb.cloud for the latest.

Still stuck?

If none of the above matches what you are seeing, contact support and include:

• Your organization name.
• What you were trying to do, and the exact message you saw.
• The time it happened, and whether it happens every time.