--- sourceDocument: Australia Build or modify applications sourceDocumentLink: https://www.servicenow.com/docs/r/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 June 15, 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 enhances your development workflow on the ServiceNow AI Platform® by automating code generation and application building tasks. However, it has certain constraints that impact deployment capabilities and performance. Understanding these limitations helps you plan deployments effectively and troubleshoot issues by balancing automated tasks with manual development steps. 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. Implement peer reviews, static checks, and validation processes. * **Partial support for app components:** Build Agent does not yet support all app files and metadata types, such as some tables, user interfaces, or advanced features. For these, continue using ServiceNow Studio. * **Security scope:** Security in apps built with Build Agent applies at the application and API level, not at granular record or field levels by default. You can extend security using agentic development techniques. * **Limited cross-product AI integration:** Build Agent can generate data models and business rules, but understanding where data is stored on the ServiceNow AI Platform is essential. * **Dependency on ServiceNow Fluent:** Build Agent's capabilities are bounded by what the ServiceNow Fluent API supports. Unsupported metadata types require precise platform-specific instructions for updates. * **Regulated environments restrictions:** Build Agent v2 relies on off-instance services that lack compliance certification for regulated hosting environments (GCC, NSC, FedRAMP). Customers in these environments must use Build Agent v1, which is certified and runs on-platform. ## Practical Guidance for ServiceNow Customers * If Build Agent cannot complete a task, perform that step directly on the ServiceNow AI Platform and continue using Build Agent for other development tasks. * Use Build Agent to enhance existing applications, such as adding business rules to current tables. * In regulated environments, continue leveraging core update sets, Git workflows, and Studio-based development alongside Build Agent v1. * Refer to ServiceNow Fluent documentation to understand Build Agent's supported capabilities and limits. * Provide feedback or report issues through the Idea portal on Now Support to help improve Build Agent. 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 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. Customers in regulated environments must remain on Build Agent v1, which runs on-platform and is certified for regulated use. 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).