API & Execution
429 Too Many Requests
429 Too Many Requests
You’ve exceeded your plan’s TPS limit. Check your current plan under Management → Billing and consider upgrading to a higher tier. Free = 10 TPS, Growth = 100 TPS, Pro = 500 TPS, Enterprise = Custom.
ENTITY_NOT_FOUND error
ENTITY_NOT_FOUND error
The resource ID doesn’t exist or belongs to a different tenant. Verify the ID by running the corresponding
list command. UUIDs are case-sensitive — copy them exactly from API responses.CANNOT_MODIFY error
CANNOT_MODIFY error
You’re trying to edit a non-DRAFT version. Published versions are permanently locked. Clone the version to create a new DRAFT: use
lexq versions clone --group-id <gid> --id <vid>.EMPTY_RULES error on publish
EMPTY_RULES error on publish
A version must have at least one rule before publishing. Add rules with
lexq rules create, then try publishing again.Rules don't match expected inputs
Rules don't match expected inputs
Run
lexq analytics requirements to see which facts the version expects. Then run a Dry Run with --debug to inspect execution traces and decision traces for each rule.POLICY_GROUP_DISABLED error
POLICY_GROUP_DISABLED error
The policy group is in
DISABLED status. Re-enable it in the Console under group settings, or via lexq groups update --id <gid> --json '{"status": "ACTIVE"}'.CLI
'lexq: command not found'
'lexq: command not found'
The CLI is not installed globally. Run
npm install -g @lexq/cli or use npx @lexq/cli instead.'API key not found' when running commands
'API key not found' when running commands
Run
lexq auth login to store your API key. The key is persisted at ~/.lexq/config.json.MCP Server — Cloud (Claude.ai)
'Authorization with the MCP server failed'
'Authorization with the MCP server failed'
'Failed to create API key' during authorization
'Failed to create API key' during authorization
Tools appear but calls return errors
Tools appear but calls return errors
Your API Key may have been revoked or the account deactivated. Remove the connector and re-authorize with a valid key.
MCP Server — Local (stdio)
MCP server starts but no tools appear
MCP server starts but no tools appear
Restart your AI client (Claude Desktop, VS Code, etc.) after adding the MCP configuration. Some clients cache tool lists on startup.
'npx: command not found'
'npx: command not found'
Node.js 18+ is required. Run
node --version to verify. If not installed, download from nodejs.org.Connection timeout or transport error
Connection timeout or transport error
The local MCP server uses stdio transport — it reads from stdin and writes to stdout. It does not open network ports. If your AI client only supports HTTP/SSE transport, use the Cloud method instead.