Skip to main content

API & Execution

You’ve exceeded your plan’s TPS limit. Check your current plan under Management → Billing and consider upgrading to a higher tier. Free = 5 TPS, Growth = 50 TPS, Pro = 200 TPS.
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.
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>.
A version must have at least one rule before publishing. Add rules with lexq rules create, then try publishing again.
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.
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

The CLI is not installed globally. Run npm install -g @lexq/cli or use npx @lexq/cli instead.
Run lexq auth login to store your API key. The key is persisted at ~/.lexq/config.json.
This is a known issue. Number formatting for table output (e.g., deltaPercentage, matchRate) will be rounded to 1 decimal place in a future release. Use --format json for raw values.

MCP Server

Restart your AI client (Claude Desktop, VS Code, etc.) after adding the MCP configuration. Some clients cache tool lists on startup.
Node.js 18+ is required. Run node --version to verify. If not installed, download from nodejs.org.
The LexQ 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, it’s not compatible with stdio mode.

Still stuck?

Visit Support to reach the LexQ team directly.