Usage-limit problems

Read the actual error code before changing a plan or repeating the request. A WordPress tool failure is not evidence that your allowance is exhausted.

PLAN_LIMIT_EXCEEDED

Ask the Agent to call get_account and review the current Workspace's limits, usage, remaining allowance, and reset time. This tool takes no website or Workspace identifier and answers only for the authenticated connection.

Open Settings → Usage & Limits in the same Workspace. Stop repeating the same request if no allowance remains. The owner can review Billing; a member should contact the owner.

A fresh retry that reaches WordPress can consume another AI Action. It cannot recover an earlier charge.

SUBSCRIPTION_INACTIVE

Have the owner review the Workspace's commercial access in Billing. This is different from an unreachable WordPress website. get_account can provide the next action available to the caller without exposing owner-only billing details to a member.

Temporary throttling

For a rate-limit response, wait for the retry delay or reset information actually returned. Reduce parallel requests before trying again. Do not keep sending the same request in a tight loop.

Usage looks unexpected

Match the Workspace and time period, then inspect Activity. A dispatched attempt may count even when the website returned an error. Discovery and pre-dispatch refusals do not count.

Record the time, code, and available request identifier for support. Read AI Actions and limits for the accounting rules.