--- sourceDocument: Brazil Build or modify applications sourceDocumentLink: https://www.servicenow.com/docs/r/application-development Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Limitations # Build Agent limitations {#ariaid-title1} Release version: Brazil 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 tool designed to assist ServiceNow developers by automating parts of the application development process. However, it has specific constraints that impact deployment capabilities and overall performance. This guide helps ServiceNow customers understand these limitations so they can effectively plan deployments and troubleshoot issues. Show full answer Show less ## General Limitations * **Human Review Required:** AI-generated code must be reviewed by developers for access control list (ACL) accuracy, security, adherence to platform conventions, and compliance with governance policies. Incorporate peer review, static code analysis, and validation steps. * **Partial Metadata Support:** Build Agent does not yet support all application files and metadata types (e.g., some tables, user interfaces, and advanced features). For unsupported elements, developers should continue using ServiceNow Studio. * **Security Model:** Security in Build Agent--developed apps is applied at the application and API level by default, without granular record or field-level controls. Developers can use agentic development with specific requests to build additional security measures. * **Cross-Product AI Integration:** Support is limited. While Build Agent can create data models and business rules, customers should understand where AI-generated app data resides within the ServiceNow AI Platform. * **Dependency on ServiceNow Fluent:** Build Agent's capabilities are tied to ServiceNow Fluent. Unsupported metadata types in Fluent cannot be updated by Build Agent unless precise platform-specific instructions are provided. ## Regulated Environments * Build Agent v2 (available from Australia Patch 0 and Zurich 8 onwards) and related components like Autonomous Engineer and Test Agent rely on off-instance services that have not passed security compliance for regulated environments such as GCC, NSC, or FedRAMP. * Customers in regulated environments must use Build Agent v1, which runs entirely on-platform and is certified for regulated use. * Core update set and Git workflows in ServiceNow Studio remain available as alternatives in these environments. * Build Agent, Autonomous Engineer, and Test Agent support the ServiceNow Protected Platform (SPP) for Australia, the EU, and Singapore from Brazil Patch 1 onward. ## Troubleshooting and Feedback If Build Agent encounters limitations during development, customers should perform unsupported steps directly on the ServiceNow AI Platform while continuing to use Build Agent for supported tasks. For troubleshooting assistance, refer to the "Issues and solutions in Build Agent" documentation. Customers are encouraged to provide feedback and suggestions via the Idea portal on Now Support to help improve Build Agent functionality. 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/TZL2Q1ti4W~tv5AczRWrlg "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/kVsDEDvwHdBvuaXkyGluvg "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/IBj_TclGYETgyAUhN5qddA "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/TC8WqJka2pR8kg1lTg2RrA "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 Brazil Patch 1, Build Agent, Autonomous Engineer, and Test Agent support ServiceNow Protected Platform (SPP) 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).