Build Agent limitations

  • Release version: Australia
  • Updated June 15, 2026
  • 2 minutes to read
    • Summarize
    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 ServiceNow app development by automating code generation and workflow creation but has certain limitations that impact deployment capabilities and performance. It complements, rather than replaces, manual development within the ServiceNow AI Platform and Studio environments.

    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-review, static checks, and validation steps.
    • Partial Metadata Support: Build Agent does not support all app files and metadata types, such as some tables, user interfaces, and advanced features. Use ServiceNow Studio for unsupported elements.
    • Security Model: Security enforcement is at the application and API level by default, not at individual record or field levels. Agentic development techniques can be used to embed finer-grained security controls.
    • Limited AI Integration: Support for cross-product AI integration is limited. Understanding data storage on the ServiceNow AI Platform is important when generating data models and business rules.
    • Dependence on ServiceNow Fluent: Build Agent’s capabilities rely on ServiceNow Fluent API support. Unsupported metadata types require explicit platform-specific instructions to update.
    • Regulated Environments Restriction: Build Agent v2 depends on off-instance services not yet certified for regulated environments like GCC, NSC, or FedRAMP. Customers in these environments must use Build Agent v1, which runs on-platform and is certified.

    Practical Considerations for ServiceNow Customers

    • When encountering unsupported steps or errors, perform those actions directly on the ServiceNow AI Platform and continue using Build Agent for the rest of the development.
    • Use Developer Sandboxes, core update set workflows, Git workflows, Instance Scan, and ReleaseOps to complement development in regulated environments where Build Agent v2 is unavailable.
    • Refer to the ServiceNow Fluent documentation to understand Build Agent’s functional boundaries and API capabilities.
    • 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

    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.

    General limitations of Build Agent

    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.
    • Limited support for cross-product AI integration.
    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

    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:

    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 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:

    • Developer Sandboxes
    • Core update set and Git workflows in ServiceNow Studio
    • Instance Scan
    • ReleaseOps

    Feedback on Build Agent

    To give feedback on Build Agent, see the Idea portal on Now Support.