--- sourceDocument: Australia Build or modify applications sourceDocumentLink: https://www.servicenow.com/docs/r/australia/application-development Release : - australia ft:locale : - en-US ft:publication_title : - Australia Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Limitations # Build Agent limitations {#ariaid-title1} Release version: Australia Updated September 22, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Build Agent limitations Build Agent is a ServiceNow AI-powered tool designed to assist with application development by automating code generation and enhancing workflows. However, it has specific limitations that affect deployment capabilities, security, and regulatory compliance. Understanding these constraints helps you plan deployments effectively and troubleshoot issues by complementing Build Agent with manual development on the ServiceNow AI Platform when necessary. Show full answer Show less ## Key limitations * **Human review required:** AI-generated code must be reviewed for access control (ACL) correctness, security, platform conventions, and governance compliance. Incorporate peer reviews, static checks, and validation steps as part of your development process. * **Partial metadata support:** Certain app files and metadata types---such as some tables, user interfaces, and advanced features---are not yet supported by Build Agent, requiring manual work in ServiceNow Studio. * **Security scope:** Security for Build Agent-developed apps is implemented at the application and API levels by default, not at granular record or field levels. You can extend security through agentic development techniques by making specific requests. * **Cross-product AI integration:** Support is limited; you should be aware of where AI-generated app data is stored on the ServiceNow AI Platform and the implications for integration. * **Dependency on ServiceNow Fluent:** Build Agent's capabilities are bounded by the ServiceNow Fluent API and metadata support. Unsupported metadata types require precise platform-specific instructions to update. * **Regulated environments restrictions:** Build Agent v2 (Australia Patch 0, Zurich 8+) and related AI agents are unavailable in GCC, NSC, or FedRAMP-regulated environments because off-instance services have not passed required security reviews. Customers in regulated environments must continue using Build Agent v1, which operates on-platform and is certified for regulated compliance. ## Practical guidance for ServiceNow customers * Use Build Agent to enhance existing applications, such as adding business rules to existing tables, while managing unsupported elements manually. * Plan for a hybrid workflow where Build Agent complements but does not replace traditional development and review processes. * For regulated environments, rely on Build Agent v1 and traditional update set or Git workflows in ServiceNow Studio. * Consult ServiceNow Fluent documentation to understand Build Agent's functional limits and prepare precise instructions for unsupported metadata updates. * Report issues or provide feedback through the Now Support Idea portal to help improve Build Agent capabilities. Plan deployments and troubleshoot issues by learning about Build Agent constraints that affect deployment capabilities and performance. ## Troubleshooting {#build-agent-limitations__section_gml_xp1_53c} If you encounter something that Build Agent can't currently do, complete that step directly on the ServiceNow AI Platform® and keep working with Build Agent for the rest of your development. Build Agent is designed to complement your workflow, not to replace it. For details on troubleshooting, see [Issues and solutions in Build Agent](https://www.servicenow.com/docs/Aj67DWPcg301wDFdAA6S4A "Identify and resolve common issues in Build Agent."). ## General limitations of Build Agent {#build-agent-limitations__id_ebf_tp1_53c} Be aware of the following limitations when using Build Agent: * AI-generated code requires human review for ACL correctness, security, platform conventions, and governance compliance. Put peer-review gates, static checks, and validation steps in place. * You still must work with builders in ServiceNow Studio for app files and metadata types not yet supported in Build Agent, such as certain tables, UIs, or advanced features. Note: Build Agent can work on existing applications. You can use Build Agent to enhance base workflows, such as creating business rules on existing tables. * Security in apps developed with Build Agent is at the application and API level, not at granular record and field level by default. However, you can use agentic development to build security onto the app by making requests. For examples, see [Example prompts](https://www.servicenow.com/docs/nscgemh4xCrbkIB1wB6iLQ "Explore example prompts for building apps, as well as adding governance, UI and other ServiceNow metadata to help you get started with prompting Build Agent."). * Limited support for cross-product AI integration. {#build-agent-limitations__ul_cyk_qp1_53c}Build Agent can generate data models and business rules. You should understand where data from your AI-generated apps is stored on the ServiceNow AI Platform. ## Build Agent and ServiceNow Fluent {#build-agent-limitations__id_uph_tp1_53c} To understand the upper limit of what Build Agent can do, review the ServiceNow Fluent documentation. If you're not familiar with the ServiceNow AI Platform, the ServiceNow Fluent documentation can help you determine what Build Agent can do. For more information, see the following topics: * [ServiceNow Fluent API reference](https://www.servicenow.com/docs/fmk8mIvf1GXcsGx7sIjD9w "Use ServiceNow Fluent APIs to define the metadata that makes up scoped applications in source code with the ServiceNow IDE or ServiceNow SDK.") * [ServiceNow Fluent](https://www.servicenow.com/docs/HcU~6LR5CHZuUX~roJ7chw "Define application metadata in source code using the ServiceNow Fluent domain-specific programming language.") {#build-agent-limitations__ul_g12_djd_c3c} If ServiceNow Fluent does not support a metadata type, Build Agent cannot update it unless you provide precise platform-specific instructions. ## Regulated environments {#build-agent-limitations__section_regulated-environments} Build Agent, Autonomous Engineer, and Test Agent depend on off-instance services that have not completed the security compliance review required for regulated hosting environments. As a result, Build Agent v2 (Australia Patch 0 and Zurich 8 and higher) is not available in GCC, NSC, or FedRAMP environments. Note: As of Australia Patch 6, Build Agent, Autonomous Engineer, and Test Agent support ServiceNow Protected Platform for Australia, the EU, and Singapore. Customers in regulated environments must remain on Build Agent v1, which runs on-platform and is certified for regulated use. Autonomous Engineer, which depends on Build Agent v2 services, is also unavailable in regulated environments. In regulated environments where Build Agent v2 is unavailable, you can continue to use the following: * Core update set and Git workflows in ServiceNow Studio. * Instance Scan {#build-agent-limitations__ul_regulated-available} ## Feedback on Build Agent {#build-agent-limitations__section_ww3_krj_ljc} To give feedback on Build Agent, see the [Idea portal on Now Support](https://support.servicenow.com/ideas).