Error Reference

Browser rendering timeout: form took too long to load

Browser rendering timeout: form took too long to load

Where this appears

This error appears in the browser console or as a user-facing message when a ServiceNow form or list view fails to render within the configured timeout period. It typically occurs during form loading operations when users navigate to records or attempt to open forms that contain complex configurations.

Sourdough
Chrome Extension

Debugging this in a real instance?

Sourdough lets you trace "Browser rendering timeout: form took too long to load" through system logs, script errors, and API health in the ServiceNow tab you are already using.

Add to Chrome

Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.

Overview
Tasks
CMDB
API
Metrics
Monitor
Internals
Instance:sourdoughdev·Version:Yokohama
Instance StateONLINE
System StatusFully Operational
Session Timeout90 minutes
Logged-In Sessions2 (20 active)
Build Nameyokohama-12-18-2024_p1
IP Address10.159.128.43
Instance HealthHealth Score: 90%
🔥 5dSourdough (Chrome Plugin)Dark Mode

Cause

Excessive client scripts executing during form load, particularly complex onLoad client scripts with heavy processing or synchronous server calls. (high likelihood)

Large number of fields on the form causing DOM rendering delays, especially forms with 100+ visible fields or complex field types like reference fields with large choice lists. (high likelihood)

Slow-performing UI policies or UI actions that execute complex server-side logic during form initialization. (medium likelihood)

Browser timeout settings configured too low in system properties, not allowing sufficient time for complex forms to render. (medium likelihood)

Database performance issues causing slow field population or reference field lookups during form loading. (low likelihood)

Fix

Step 1: Check the browser developer console for specific JavaScript errors or performance warnings that may indicate which scripts are causing delays.

Step 2: Navigate to System Definition > Client Scripts and review all onLoad client scripts for the affected table, looking for synchronous GlideAjax calls or complex processing loops.

Step 3: Examine the form layout by going to System Definition > Forms and checking the number of fields, sections, and related lists configured for the problematic form view.

Step 4: Review UI policies at System Definition > UI Policies for the table, focusing on policies that run on load and contain complex server-side scripts or multiple field operations.

Step 5: Check system properties for browser timeout settings by searching for 'glide.ui.security.allow_codetag' and 'glide.ui.form_rendering_timeout' in System Properties.

Step 6: Test form performance by temporarily deactivating suspected client scripts or UI policies to isolate the problematic component.

Step 7: Optimize identified issues by converting synchronous client script calls to asynchronous, reducing form complexity, or improving UI policy efficiency.

Step 8: Monitor system performance through System Diagnostics > Performance Analytics to identify any underlying database or system resource constraints.

Test Your Knowledge

Quick 3-question quiz. See how your ServiceNow skills stack up.

Question 1 of 3Performance

A list view on a table with millions of records is slow. Best fix?

Select an answer to continue