Limits and troubleshooting

Identify whether the failure happened during connection, tool discovery, authorization, validation, creation, or background processing. Retain the exact error before retrying.

Connection and authorization

Use https://mcp.justlandit.com/mcp with a compatible remote client. Check organization policy and authorize the intended Landit account. Reconnect if the client reports expired access. The assistant client connects through its own authorization flow.

Tool and input errors

Error or symptom	Recovery
`template_not_found`	List accessible templates and use the explicitly selected slug.
`invalid_arguments`	Check required fields, nonblank values, and paired CRM identifiers.
Run not found	Distinguish enrichment UUID, PageRun UUID, and template-generation UUID; confirm account.
Empty Page search	Check combined exact filters and pagination.
Asset update invalid	Inspect ownership and shared-template or teammate dependencies.

Processing failures

Use the existing identifiers to inspect progress and failure reasons. Batch acceptance starts background processing. Page generation and CRM writeback have separate states, so a completed Page can be available while CRM delivery needs attention.

After a timeout or an ambiguous response, search for existing work before another enrich_prospects call. Follow client retry instructions for throttling rather than inventing a fixed rate limit. Send the client, tool, time, and sanitized error through Get help when unresolved.