Skip to main content
An action can be blocked by plan, role, credits, target state, provider readiness, or product availability. Use the visible reason to choose the narrowest recovery path.

​
A lock or Upgrade control appears

The current workspace plan does not include the reading or action.
  1. Confirm the active workspace.
  2. Open the plan explanation.
  3. Review the current catalog in Billing.
  4. Ask the workspace Owner to make any billing change.
  5. After a confirmed upgrade, let any activation run prepare the new surface.
An upgrade does not guarantee provider coverage or make a coming-soon surface available.

​
Only the Owner can continue

Member management and billing changes are Owner-only. An Admin should send the workspace name and intended change to the Owner rather than attempting to bypass the role boundary. Product actions can have different role rules. The server’s current catalog and refusal are authoritative.

​
No credits are available

Open Billing from the credit indicator. Distinguish:
  • no allowance on the current plan;
  • a metered allowance that reached its limit;
  • an unlimited plan;
  • a run that stopped after exhausting credits.
Wait for the displayed reset or ask the Owner to review plan options. Do not retry a stopped action until capacity is available.

​
The target is already busy

Alesta protects individual targets from overlapping writes.
  • Wait for Updating…, Rewriting…, Researching…, Removing…, or Improving… to finish.
  • For competitors, a batch change locks the whole set.
  • Refreshing does not clear the server lock.
  • Follow the existing action instead of submitting a second brief.

​
The action is unavailable

Unavailable can mean:
  • the service is not deployed;
  • the provider or platform path is not commercially ready;
  • a required connection or resource is missing;
  • the feed revision is no longer active;
  • the server catalog does not offer the action in this environment;
  • a source limitation prevents the requested work.
Read the reason and complete only the requested prerequisite. If the action is unsupported, connecting another account or upgrading will not necessarily help.

​
The surface says Coming soon

Coming soon is a product boundary, not a plan gate. The current Articles row is an example. Do not purchase a plan or authorize a provider expecting a coming-soon control to activate.

​
A paid action failed

Review the error and the current content before retrying. Possible conditions include:
  • the model output could not be completed;
  • the action was rejected by validation;
  • the target changed before the request finished;
  • the provider request failed;
  • payment for an immediate plan change failed;
  • the result is unknown and an external system must be checked first.
For a GitHub result marked unknown, inspect the repository before another attempt. The same request identity must not create a duplicate.

​
Escalate safely

Contact support when the visible state contradicts the known plan, role, credits, or provider account. Include the workspace, action title, target, approximate time, and exact visible message. Never include credentials, access tokens, session cookies, private keys, or payment-card details.

​
References