Fix common errors in Wavefront

Most errors in Wavefront say what to do next in the message itself. This page covers the ones people run into most, with what each means and how to fix it. Developers can find every error code in the errors reference.

“Choose a plan” or plan_required

What it means. The workspace has no plan: the 7-day trial ended, or the plan was cancelled. Drafting, the strategist, autopilot, the REST API and the MCP server are paused. Agents and scripts see 402 plan_required.

Fix. An owner opens Billing and chooses Choose a plan. Your documents, strategy and drafts are all still there. See your plan and credits.

Not enough credits, or insufficient_funds

What it means. The balance can’t cover the minimum for that kind of draft. Scripts see 402 insufficient_funds.

Fix. An owner buys a credit pack under Billing → Add credits, or waits for next month’s credits. See credit packs and rollover.

Daily or concurrency limit reached

What it means. The workspace hit its Daily spend (credits) limit for the last 24 hours, or too many drafts are running at once.

Fix. Wait and try again, or an owner raises the limits under Settings → Limits and autopilot → Spend and concurrency.

insufficient_scope from an AI agent

What it means. The agent’s connection was granted read access only, so write tools such as drafting are refused with 403 insufficient_scope.

Fix. Reconnect the agent and leave write checked on the consent page. Many agents ask you to grant write access automatically. If the agent uses an API key, an owner gives the key a write scope. See agent connection problems.

Human approval required

What it means. An agent or API key tried to approve a version. Only an owner or editor signed in to the web app can approve. Scripts see 403 human_approval_required.

Fix. Open the draft in the web app and approve it there. The agent can then publish it. The same goes for withdrawing a post, posting to social networks and sending newsletters.

You can’t do something your teammate can

What it means. Your role doesn’t allow it. Viewers can read and comment only. Settings, destinations, billing and the team are for owners.

Fix. Ask an owner to change your role on the Team page. See signing in and roles.

A draft failed

What it means. The draft stopped without a version. The draft page says why. Common causes:

• A document it needs is missing, too large or invalid, for example a writing rule with a broken pattern.
• An answer to its questions couldn’t be used.
• A temporary problem with a provider.

Fix. Read the error on the draft page, fix the cause if it names one, then draft again. A draft that failed because of a problem on our side isn’t charged. One that failed because of something in the workspace is charged for the work done, at a reduced rate.

Related statuses:

• Expired: nobody answered its questions within 14 days. Draft it again.
• Stopped at the budget limit: it ran out of credits partway. A partial version can’t be approved. Request a revision or start again.

A calendar slot was missed

Overdue means a post’s date passed with no draft. Draft it now, move it to a new date, or remove it. Turning on autopilot drafts posts before they’re due.

Missed means a post was approved but never published by its date. Publish or schedule it from the draft’s Publishing box. To stop this happening, an owner turns on Publish approved posts on their calendar date in autopilot settings.

When autopilot fills the calendar from the backlog and its draft for a slot fails or stops to ask questions, it gives the slot to the next idea.

A destination rejected the publish

What it means. The destination refused the post, or the connection stopped working. The publication shows the step that failed and the reason.

Fix, by cause:

• Credentials refused or expired. The destination shows Reconnect needed. An owner opens Edit in Settings → Publishing and reconnects or pastes a new token.
• The text breaks the destination’s rules, such as a character limit or a required field. Request a revision that fixes the flagged text.
• The slug is already taken at the destination. Change the slug in a revision, or remove the old post there.
• Another publish of the same item is running. Wait for it to finish.
• A post may have gone out but wasn’t confirmed. Wavefront never posts twice. Check the destination before publishing again, then remove the extra post there if needed.

Warnings found after a page went live, such as a missing meta description or a broken image, never undo the publish. Fix them at the destination or in a revision.

Still stuck

Email support@adwave.com with the workspace name, what you were doing, the time, and the exact message you saw.