Issues and solutions in Build Agent

  • Release version: Australia
  • Updated June 24, 2026
  • 4 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 Issues and solutions in Build Agent

    This guide addresses common issues encountered when using Build Agent within ServiceNow, providing practical troubleshooting steps to quickly identify and resolve problems. It emphasizes a structured debugging approach and captures essential information for effective support escalation.

    Show full answer Show less

    General Debugging Approach

    • Copy the exact error message and paste it into the Build Agent chat to leverage its diagnostic capabilities.
    • If unresolved, follow a structured process: reproduce the error consistently, review debugger output and logs, verify access and configuration, and check for known issues.
    • Test hypotheses from simplest (access or role issues) to more complex (configuration, naming conflicts, logic edge cases).
    • If unresolved after multiple attempts, start a new chat with a focused prompt including saved debugging details to assist Now Support.

    Common Issues and Practical Resolutions

    • ServiceNow Otto panel not visible: Confirm required plugins (snglider, snbuildagent, snnowcreator) and admin roles are assigned. Refresh or re-login. Capture exact errors, release version, and user roles if issue persists.
    • Build Agent unresponsive: Clear browser cache, try alternate browsers, and check ServiceNow status page. If unresolved, capture hung requests, browser version, and status state.
    • Scope or name conflict: Verify if the app scope or name is already used. Allow Build Agent to self-correct or choose a unique name. Capture conflicting names and triggering actions if needed.
    • Stuck in error loop: Use Git checkpoints or rollback updates. Start a new conversation with specific error details and recent commits.
    • App not deploying: Check build output for errors before deployment. Run ServiceNow SDK build, verify update sets, and deploy sequentially. Use Build Agent chat to fix build failures. Capture build logs, SDK version, and update set status if issues persist.
    • Empty UI page: Inspect browser console for errors. Paste console errors into Build Agent chat for resolution. Capture full console output if unresolved.
    • Context limit exceeded: If receiving context window errors, start a new chat describing the application. Build Agent will continue from the last known point. Capture last prompt and build summary if issues continue.
    • Out of prompts: Verify remaining prompt count within the 30-day cycle. Wait for reset or upgrade plan. Capture entitlement state and reset date if necessary.
    • Rate limit error: Occurs when too many requests are sent. Wait briefly before retrying. Capture error message and timestamp if needed.
    • Unsupported configuration: Confirm requested metadata or features are supported. Perform unsupported steps directly on the platform and continue with Build Agent. Capture configurations and workarounds if required.
    • Missing dependencies (ServiceNow IDE): Review package.json entries referenced by Build Agent. Allow self-correction or manually add missing packages and run npm install. Capture missing module names and errors if unresolved.
    • Long-running prompt times out: Check session timeout settings. For labs/workshops, set glide.ui.sessiontimeout to 1440 minutes after coordinating with platform admins. Capture session length and timeout prompts if issue persists.

    What to Expect

    Following this guidance enables ServiceNow customers to methodically diagnose and resolve Build Agent issues, reduce downtime, and improve development productivity. When issues require escalation, detailed captured information ensures faster and more accurate support from Now Support.

    Identify and resolve common issues in Build Agent.

    General debugging approach

    Copy the error message and paste it into the Build Agent chat. Build Agent can often diagnose and fix the issue directly. If not, the error message is your starting point for debugging.

    If several fixes in the same conversation don't resolve the issue, use a structured approach before starting a new chat.

    Tip:

    Use the following prompt to structure your debugging session:

    I'm seeing this error: [paste exact error]. This happens when: [describe scenario]. Before suggesting fixes: 1) Help me reproduce this consistently. 2) Review the debugger output and logs. 3) Check for access or configuration issues. 4) Examine if this is a known issue.

    Test hypotheses from simplest to most complex:

    • Is this an access or role issue?
    • Is this a configuration problem?
    • Is this a naming convention mismatch?
    • Is this a logic edge case?

    If structured investigation doesn't resolve the issue within a few attempts, start a fresh conversation with a more specific prompt.

    Save any debugging information to convey if you need to contact Now Support.

    Issues and solutions

    Table 1. Build Agent issues
    Issue Resolution
    ServiceNow Otto panel not visible
    • Quick check: Required plugins are installed and your account has the required roles. The ServiceNow IDE needs the admin role plus the documented Build Agent plugins (sn_glider and sn_build_agent for Trial; sn_now_creator for Premium). In ServiceNow Studio, confirm you're on a supported release.
    • Try: Refresh the page or sign out and back in.
    • If still failing, capture: The exact error or behavior, your release, and the role list on your user.
    Build Agent unresponsive
    • Quick check: Browser cache and the active session.
    • Try: Clear the cache, try a different browser, and check the ServiceNow status page for service announcements.
    • If still failing, capture: The request that hung, your browser version, and the ServiceNow status state.
    Scope or name conflict
    • Quick check: Whether the scope or app name is already in use on the instance.
    • Try: Let Build Agent self-correct with a unique scope, or pick a new name and try again.
    • If still failing, capture: The conflicting scope or app name and the action that triggered it.
    Stuck in error loop
    • Quick check: How many fixes Build Agent has attempted on the same symptom.
    • Try: Use Git checkpoints or update set rollback to revert, then start a fresh conversation that names the specific error.
    • If still failing, capture: The exact error text, recent commits, and a brief description of what you were trying to accomplish.
    App not deploying
    • Quick check: Build output for errors before deploying. Build Agent only deploys the latest successful build. If your updates are not available after deployment, the build may have failed even though the deployment succeeded.
    • Try: In the ServiceNow IDE, run ServiceNow SDK build first, check errors, then deploy and install in sequence. In ServiceNow Studio, confirm your update set is current and complete. Paste any error messages into the chat panel and ask Build Agent to resolve the build issues and redeploy. For more information, see Deploying what you built with Build Agent.
    • If still failing, capture: The build log, your SDK version, and your update set state.
    Empty UI page
    • Quick check: The browser console for errors.
    • Try: Open the browser console, copy the error messages, paste them into the chat panel, and ask Build Agent to fix the UI page.
    • If still failing, capture: The full browser console output and the prompt that produced the empty page.
    Context limit exceeded
    • Quick check: Whether you have received a Context Window Exceeded error. Build Agent maintains a history of your session and can resume from the point of failure, but has a context limit.
    • Try: Open a new chat window and describe the application again. Build Agent does not retain context from the previous session, but it reviews the work already done and continues from where it stopped.
    • If still failing, capture: The last prompt before the error and a summary of what had been built.
    Out of prompts
    • Quick check: Your remaining prompt count for the current 30-day cycle.
    • Try: Wait for the cycle to reset, or upgrade to ServiceNow Otto for Creator. Plan approvals do not count against your prompt allotment; only submitted prompts do.
    • If still failing, capture: Your entitlement state and the cycle reset date.
    Rate limit error
    • Quick check: Whether the model provider is receiving too many requests.
    • Try: Wait a minute or two before trying again.
    • If still failing, capture: The exact error message and the time it occurred.
    Unsupported configuration
    • Quick check: Whether the requested metadata or feature is in the supported list.
    • Try: Complete that step directly on the platform, then continue with Build Agent for everything else.
    • If still failing, capture: The configuration you needed and the workaround you used.
    Missing dependencies (ServiceNow IDE)
    • Quick check: package.json for the entries Build Agent referenced.
    • Try: Let Build Agent self-correct first. If that does not resolve it, add the package manually and run npm install.
    • If still failing, capture: The missing module name and the install error output.
    Long-running prompt times out
    • Quick check: Your session timeout setting.
    • Try: For labs and workshops, set glide.ui.session_timeout to 1440 in the System Property [sys_properties] table. Coordinate with the platform admin on a shared instance before changing it.
    • If still failing, capture: The session length and the prompt that timed out.