Across CRM Insights, Agent Studio, and AI-powered Workflows, Zoho Zia Agents operate under a set of strict execution rules governing how they build database queries and carry out multi-step actions. These rules exist to prevent hallucinated queries, stop agents getting stuck in infinite loops, and keep every generated query genuinely compliant with the underlying database structure.
1. Natural Language to Database Query Rules (COQL Engine)
When a Zia Agent translates a plain-language request into query language, such as COQL (CRM Object Query Language), it works within strict single-query validation boundaries.
- Mandatory RAG pre-fetch. Before generating any database query, the agent must first run a retrieval-augmented generation call against the COQL Knowledge Base to fetch the valid modules, explicit field details, and syntax rules it needs to build a correct query.
- Strict conditional structure. Free-form boolean logic isn't permitted. Every generated query must express its conditions using explicit, strictly nested grouping, such as (A and (B and C)) or ((A and B) and C), rather than ambiguous flat logic.
- Explicit column declarations. Wildcard SELECT operations (SELECT *) are forbidden. Every required column must be explicitly named in the query.
- JOIN and function restrictions. A single query execution can use a maximum of 5 base JOINs, and functions such as YEAR() or MONTH() cannot be used inside conditions.
- Default limits. If a user asks for records without specifying how many, the agent must strictly apply a LIMIT of 10 rather than returning an unbounded result set.
The 3-iteration self-correction cap: If a constructed query fails execution validation against the Knowledge Base rules, the agent is allowed up to 3 retry or reconstruction attempts. If it still hasn't produced a valid query after those 3 attempts, it must abandon that query execution entirely and fall back to alternative processing, rather than continuing to retry indefinitely.
2. Workflow and Automation Single-Action Limits
When Zia Agents execute actions inside automated workflows, such as those in Zoho Desk or Zoho CRM, the platform applies strict action-type constraints:
- One action type per rule. A single workflow rule can only include a maximum of one instance of each type of Zia action at a time.
- No action duplication. An individual Zia action, such as Data Extraction, Field Prediction, Auto Triage, or Email Auto-Reply, can only be used once per workflow rule execution.
- Execution cap. A global daily cap of 1,000 executions per organisation applies across all Zia workflow automation actions combined.
3. Session Key and Single Trigger Isolation
When Zia Agents are triggered autonomously by business events, such as a lead being created or a ticket being updated, two mechanisms keep executions properly isolated:
- Session Key grouping. Triggers use the Record ID as the default Session Key, ensuring every event execution tied to a single record runs within its own isolated context window, without cross-contaminating other agent interactions happening elsewhere.
- Field selection minimisation. To avoid exceeding the underlying language model's context limits, or generating unnecessary sub-queries, triggers can be scoped to pass only specific fields relevant to the task, rather than the entire record.
Need help? 1 Cloud Consultants can help you design Zia Agent workflows and queries that work reliably within these execution limits, from COQL query structure to trigger scoping.
Book a discovery call with 1 Cloud Consultants.