Skip to main content

​
API & Execution

Two conditions return 429 with code C-007.Your plan’s TPS limit. Check your current plan under Management → Billing and consider upgrading. See Rate Limits for the per-plan table. Batching also helps: batch and composite calls count as one request against TPS.Edge protection. Very high request rates from a single IP are throttled before reaching the API, independent of your plan. Upgrading does not raise this ceiling, and normal application traffic does not reach it. Contact support if you see this consistently.
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 split is decided by context.trafficKey on each execution request. If your requests do not carry it, or carry it inside facts instead of context, no request is ever assigned to the test version. The test still reports as running and logs keep accumulating, so nothing in the response says anything is wrong.The server logs a warning on every affected request:
Batch calls read sharedContext.trafficKey, not the per-request context. See Traffic Identity Key.
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.

​
MCP Server — Cloud (Claude.ai)

Remove the LexQ connector in Settings → Connectors, then re-add https://mcp.lexq.io. Ensure you complete both the login step and the API Key selection/generation step before clicking Authorize.
Your account may have reached the API Key limit. Go to Console → Management → API Keys and delete unused keys, then try again.
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)

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 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.

​
Still stuck?

Visit Support to reach the LexQ team directly.