Build Agent limitations

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:

• ServiceNow Fluent API reference

• ServiceNow Fluent

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

Feedback on Build Agent

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

Parent Topic:Exploring Build Agent