ACL evaluation failed: access denied for table incidentThis error appears in the ServiceNow application log when a user or service account attempts to access a record but lacks proper permissions. It commonly occurs during CRUD operations on tables and can be seen in System Diagnostics > Log > Application Log or in browser console during form loads and list views.→API key invalid or expired: request rejectedThis error appears in ServiceNow system logs under System Diagnostics > Log > Application Log when external systems attempt to authenticate using REST API keys or OAuth. The error occurs during inbound web service calls, REST API requests, or third-party integrations when the provided API key cannot be validated against active records in the system.→ATF test suite failed after upgrade: automated tests not passingThis error appears in the Automated Test Framework (ATF) test results after a ServiceNow platform upgrade when previously passing test suites now fail. The error is typically visible in the ATF Test Results table (sys_atf_test_result) and in the Test Runner interface under System Applications > Automated Test Framework > Run Test Suite.→Access denied: insufficient privileges for the operationThis error appears in the browser console, system logs, or as a user-facing error message when attempting to execute UI actions, trigger business rules, or access scripted REST API endpoints. It typically occurs during form submissions, button clicks, or API calls when the current user lacks the required elevated privileges defined in the script or configuration.→Application scope access error: permission denied for target scopeThis error appears in the ServiceNow System Log under System Diagnostics > Log > Application Log when a scoped application script attempts to access resources in another application scope. It commonly occurs during script execution in Business Rules, Script Includes, UI Actions, or scheduled jobs when cross-scope access policies are not properly configured.→Approval stuck in pending state: approver not notifiedThis error appears in approval workflow logs and system diagnostics when an approval record remains in the Requested state without sending notifications to designated approvers. The error is typically identified through workflow log analysis or when users report missing approval notifications.→Attachment too large: file exceeds maximum allowed sizeThis error appears in integration logs, ECC queue processing records, or web service responses when attempting to transfer file attachments through inbound or outbound integrations. The error occurs during REST API calls, import operations, or when external systems attempt to send attachments to ServiceNow that exceed configured size limits.→Base system update conflict: customization overlaps with upgrade changeThis error appears in the upgrade log during ServiceNow instance upgrades when the system attempts to update a base system record that has been customized. The upgrade process automatically skips the conflicting update and records the conflict for manual administrator review and resolution.→Browser rendering timeout: form took too long to loadThis 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.→CI class not found: discovery target class does not exist in CMDBThis error appears in the Discovery Status records, ECC Queue error messages, and System Log during discovery operations. It occurs when Discovery probes identify configuration items that reference CI classes not present in the CMDB dictionary or class hierarchy.→CMDB health audit failure: data quality rules violatedThis error appears in the CMDB Health Dashboard and System Log when automated CMDB health audits detect configuration items that violate established data quality rules. The error typically occurs during scheduled health audits or when manually running CMDB health checks through Configuration > CMDB Health.→CMDB identification created duplicate CI: IRE deduplication failedThis error appears in the CMDB Identification and Reconciliation Engine (IRE) logs during discovery operations or CI reconciliation processes. The error occurs when the IRE creates a new CI record instead of updating an existing one due to failed identification matching rules.→CMDB reconciliation error: conflicting data from multiple sourcesThis error appears in the IRE (Identification and Reconciliation Engine) logs and CMDB reconciliation reports when multiple data sources provide different values for the same CI attribute with equal precedence. The error typically occurs during scheduled discovery runs, manual CMDB reconciliation processes, or when viewing reconciliation results in the CMDB Dashboard.→CSV import encoding error: invalid character in fileThis error appears in the ServiceNow import log when attempting to import CSV files through System Import Sets or Data Sources. The error is displayed in the Transform History record or Import Set table, indicating the CSV file contains characters that cannot be parsed as UTF-8 encoding.→Cache flush required: stale cache causing unexpected behaviorThis error typically appears in the Application Log under System Diagnostics > Log > Application Log or in browser developer console during application runtime. It occurs when ServiceNow detects that cached data is outdated after configuration changes, causing inconsistent behavior in forms, business rules, or system operations.→Cannot insert: duplicate value violates unique constraintThis error appears in ServiceNow system logs and application logs when executing GlideRecord insert() operations. The error occurs during script execution in Business Rules, Script Includes, or other server-side scripting contexts when attempting to create records that violate unique field constraints.→Cannot read property of null: TypeError in scriptThis error appears in the System Log under System Diagnostics > Log > Application Log when server-side scripts attempt to access properties or methods on null objects. It commonly occurs in Business Rules, Script Includes, Scheduled Jobs, and other server-side scripting contexts during record operations or API calls.→Cannot set value: field is read-onlyThis error appears in ServiceNow system logs, browser console, or script execution logs when a server-side or client-side script attempts to modify a field that has been marked as read-only. It commonly occurs during Business Rule execution, Script Include operations, or when using GlideRecord operations on restricted fields.→Catalog client script error: script failed on catalog formThis error appears in the browser console when a client script on a Service Catalog item form encounters a JavaScript runtime error. The error typically occurs during form loading, field value changes, or form submission when catalog variable interactions fail. Users may notice that catalog form behaviors like field visibility, mandatory settings, or value calculations stop working properly.→Catalog item not visible: item not appearing in service catalogThis issue occurs when users cannot see an active catalog item in the Service Portal or classic Service Catalog interface, even though the item appears active in the backend. The problem manifests as missing catalog items during normal catalog browsing or search operations.→Certificate chain validation failed: untrusted root CAThis error appears in ECC queue error logs, system logs under System Diagnostics > Log > Application Log, and REST API response errors when ServiceNow attempts to establish SSL connections to external systems. It typically occurs during outbound integrations, web service calls, or certificate-based authentication processes.→Client script blocked: cross-origin request rejectedThis error appears in the browser console when client scripts, UI pages, or Service Portal widgets attempt XMLHttpRequests to external domains. The error occurs when ServiceNow's Content Security Policy (CSP) or CORS configuration blocks the cross-origin request for security reasons.→Client script not executing: expected behavior not occurring on formThis error manifests when expected client-side behavior does not occur on ServiceNow forms, typically noticed during form load, field changes, or form submission. The error may appear in the browser console or be observed through missing form functionality. Users report that scripts that previously worked or should work based on conditions are not triggering their intended actions.→Clone target error: clone operation failed on target instanceThis error appears in the ServiceNow Clone Monitor (System Clone > Clone Monitor) and in system logs during instance cloning operations. It occurs when attempting to clone data from a source instance to a target instance, typically during scheduled clone jobs or manual clone operations initiated through the instance management portal.→Connection pool exhausted: no available database connectionsThis error appears in the ServiceNow application logs and system diagnostics when the database connection pool reaches its maximum capacity. Users may experience slow page loads, timeouts, or complete inability to access the ServiceNow instance during peak usage or when problematic queries consume available connections.→Cross-scope access denied: script cannot access global scopeThis error appears in the Application Log under System Diagnostics > Log > Application Log when a scoped application script attempts to access resources in the global scope or another application scope. The error typically occurs during script execution in Business Rules, Script Includes, UI Actions, or Client Scripts when cross-scope access policies are not properly configured.→Data source connection failed: cannot reach JDBC or LDAP sourceThis error appears in the System Log and Import Set Run History when a scheduled import or transform job attempts to connect to an external JDBC database or LDAP directory server. The error typically occurs during the data collection phase of import set operations and may also appear in MID Server logs if using an external MID Server for the connection.→Data type mismatch: expected integer, got stringThis error appears in the ServiceNow system logs, application logs, or browser console when server-side scripts attempt to assign string values to integer-type fields. It commonly occurs during GlideRecord operations, Business Rule execution, or Transform Map processing when field type validation fails.→Database index not used: query performing full table scanThis error appears in the System Log under System Diagnostics > Log > Application Log when queries execute against large tables without utilizing available indexes. It commonly occurs during list view loading, reporting operations, or scheduled jobs that query tables with millions of records.→Dependent relationship missing: CI relationship not createdThis error appears in Discovery logs and ECC queue processing when Discovery successfully identifies two Configuration Items but fails to create the expected relationship between them in the CMDB. It commonly occurs during infrastructure discovery operations when dependency mapping is enabled.→Dictionary override conflict: field definition conflicts with base systemThis error appears in the System Log during ServiceNow instance upgrades when the system detects conflicting field definitions between custom dictionary overrides and updated base system configurations. The error is typically found in the upgrade logs and may also appear in the System Diagnostics > Log > Application Log during post-upgrade validation.→Discovery credential error: authentication failed for target deviceThis error appears in the Discovery Status table (discovery_status) and ECC Queue logs during Discovery runs when attempting to connect to target devices. The error is visible in the Discovery Logs and may also appear in the MID Server logs when credential authentication fails during device scanning or data collection.→Discovery pattern failed: pattern did not match target deviceThis error appears in the Discovery Status under Discovery > Status > Discovery Status, in ECC Queue records, and in Discovery logs when a Discovery or Service Mapping pattern cannot successfully identify or classify a target CI. The error occurs during scheduled discovery jobs or manual discovery operations when pattern matching logic fails.→Duplicate CI detected: multiple records represent the same configuration itemThis error appears in the CMDB Health Dashboard, Discovery logs, and during CI creation or update operations. It occurs when ServiceNow Discovery or manual processes create multiple CI records that represent the same physical or logical configuration item in the cmdb_ci table or its extended tables.→ECC queue stuck: input messages not being processedThis error appears in the System Log under System Diagnostics > Log > Application Log when ECC queue records accumulate without being processed. It typically occurs during integration operations when messages remain in Ready or Processing state for extended periods, indicating the ECC queue processor has stopped functioning properly.→Email attachment blocked: file type not allowedThis error appears in the System Log under System Diagnostics > Log > Application Log when ServiceNow attempts to process an inbound or outbound email notification containing an attachment. The error occurs during email processing when the attachment file extension is found on the system's blocked extensions list, preventing the email from being sent or received successfully.→Email notification not sending: outbound email failedThis error appears in the System Log under System Diagnostics > Logs > System Log when ServiceNow attempts to send an email notification but fails during the outbound email process. The error is logged when the email notification record is created successfully but cannot be delivered due to SMTP or email account configuration issues.→Event not processed: event queue entry remains unhandledThis error appears in the System Log under System Diagnostics > Log > Application Log when events written to the sysevent table are not processed by their corresponding event registrations or notification rules. The error typically occurs during automated workflows, business rule executions, or scheduled job processing when the event processing engine cannot find or execute the appropriate handler.→Excel import truncation: field value exceeded maximum lengthThis error appears in the Import Set table records or in the System Log during Excel file imports when processing data through Data Sources. The error occurs when ServiceNow attempts to insert data from Excel cells into target table fields that have defined maximum length restrictions.→Family release patch conflict: patch cannot be applied to current versionThis error appears in the System Upgrade History table and upgrade logs when attempting to apply a hotfix or patch through HI (Hotfix Installer) or manual patch installation. The error occurs during the patch validation phase before actual installation begins, typically visible in the System Log under System Diagnostics > Log > Application Log.→Field not found on table: invalid column referenceThis error appears in the System Log under System Diagnostics > Log > Application Log when server-side scripts attempt to access table fields that don't exist. It commonly occurs during Business Rule execution, Script Include calls, or background script operations when using GlideRecord methods like getValue() or setValue().→Flow Designer connection error: cannot load flowThis error appears in the Flow Designer interface when attempting to open or edit flows, typically displaying as a notification banner or modal dialog. The error occurs when the Flow Designer UI cannot establish proper communication with the backend services or retrieve flow definition data from the database.→Flow action failed: action returned an errorThis error appears in Flow Designer execution logs when a flow action encounters an exception during runtime. It is visible in the Flow Context and Execution Details of the flow instance, and may also appear in the System Log under Application Logs.→Flow data pill resolved to null: expected value not availableThis error appears in the ServiceNow Flow Designer execution details when a data pill reference returns null during flow runtime. The error is displayed in the flow execution history under Process Automation > Flow Designer > Executions, and may also appear in the Application Log under System Diagnostics > Log > Application Log.→Flow execution timeout: flow exceeded allowed execution timeThis error appears in the Flow Designer execution details and System Log under System Diagnostics > Log > Application Log when a Flow Designer flow exceeds the maximum execution time limit. The error occurs during flow runtime when actions like Wait for Condition, HTTP requests, or subflow calls take too long to complete or when the overall flow execution exceeds system-defined timeout thresholds.→Flow trigger not firing: record-based trigger condition not metThis error appears in the Flow Designer execution details or System Log when a record-based flow trigger fails to activate despite record operations occurring. It indicates the trigger condition evaluated to false when a record was created, updated, or deleted on the specified table.→Form not rendering: form view configuration errorThis error appears in the browser console or system logs when a form fails to load properly in the ServiceNow interface. It typically occurs when users attempt to open a record form, create a new record, or navigate to a form view that has configuration issues with its layout or field definitions.→Form section not showing: section hidden or missingThis error typically appears when users cannot see expected form sections on records, or when developers notice missing sections during form configuration. The issue manifests in the ServiceNow interface where form sections that should be visible are either completely absent or hidden from view.→GRP condition evaluation error: syntax error in conditionThis error appears in the ServiceNow system logs and application logs when a condition field containing JavaScript code fails to execute due to syntax errors. It commonly occurs during record operations like insert, update, or display when ACL conditions, business rule conditions, or assignment rule conditions are evaluated.→Garbage collection pause: GC event causing request delaysThis error appears in the ServiceNow system application logs, typically found under System Diagnostics > Stats > Memory Usage or in the instance health monitoring dashboards. It occurs during JVM garbage collection events that pause application processing, causing user requests to queue up and experience noticeable latency spikes.→GlideRecord query returned no results for expected recordThis error appears in ServiceNow server-side scripts, Business Rules, Script Includes, and client scripts when a GlideRecord query fails to return expected data. The error typically shows in the System Log under System Diagnostics > Log > Application Log or in script debugging output when developers expect at least one record but get zero results.→HTTP timeout: outbound request exceeded timeout limitThis error appears in the System Log under System Diagnostics > Log > Application Log when ServiceNow makes outbound HTTP/REST calls to external systems. It commonly occurs during integrations, scheduled imports, web service callouts, or when using REST Message records that fail to complete within the configured timeout period.→Homepage widget error: widget failed to load on homepageThis error appears on the ServiceNow homepage when a widget fails to render properly, typically displaying as a blank widget area or error message within the widget container. The error may also be logged in the browser console or appear in the Application Log under System Diagnostics > Log > Application Log during homepage loading.→Horizontal discovery pattern timeout: scan did not completeThis error appears in the Discovery Log (Discovery > Status) and in ECC Queue records when a horizontal discovery pattern fails to complete within the configured timeout period. It occurs during scheduled discovery operations or manual discovery scans when scanning IP ranges for devices and configuration items.→IP access control: your IP address is not allowedThis error appears in the browser when attempting to access a ServiceNow instance, typically displayed as a system error page or login screen message. It occurs during initial connection attempts before authentication and is logged in the System Log under Security entries.→Illegal access to Java package: access deniedThis error appears in the System Log under System Diagnostics > Log > Application Log when server-side JavaScript attempts to import or instantiate Java classes. It commonly occurs during execution of Business Rules, Script Includes, Scheduled Jobs, or other server-side scripts that try to access restricted Java packages.→Import set coalesce failure: coalesce field not found in target tableThis error appears in the Import Set transform log during data import operations when processing transform maps. It occurs when ServiceNow attempts to execute the coalesce operation but cannot locate the specified field in the target table schema.→Import set transform error: mapping failed for rowThis error appears in the Import Set Transform Log and System Log when a transform map fails to process a specific row during import set transformation. The error is typically visible in the Import Set table record's transform log or in the System Diagnostics > Log > Application Log when running scheduled imports or manual transformations.→Inbound email action not triggered: condition not metThis error appears in the Email Log (sys_email_log) and System Log when an inbound email arrives but fails to trigger the expected email action. The error indicates that while an email action was evaluated, its conditions were not satisfied to execute the action.→Integration Hub spoke action failed: spoke returned error responseThis error appears in Flow Designer execution details when a spoke action encounters an issue and returns an error response. The error is visible in the flow execution log and action output data pills within the Flow Designer interface. It occurs during flow runtime when the Integration Hub attempts to execute spoke actions against external systems or ServiceNow applications.→Invalid GlideRecord operation: cannot update without valid sys_idThis error appears in ServiceNow system logs, script debugger output, or browser console when executing server-side scripts. It occurs during GlideRecord operations in Business Rules, Script Includes, Scheduled Jobs, or other server-side scripting contexts when attempting to update or delete records.→Invalid table name: table does not existThis error appears in ServiceNow system logs, browser console, or script execution logs when attempting to instantiate a GlideRecord object with a non-existent table name. It commonly occurs during script execution in Business Rules, Script Includes, UI Actions, or background scripts when the specified table cannot be found in the instance.→JSON parse error: response body is not valid JSONThis error appears in ServiceNow application logs and REST message logs when an outbound REST call expects a JSON response but receives HTML, XML, or malformed content instead. The error typically occurs during REST API integrations, business rule executions, or scheduled import operations that make external web service calls.→JavaScript SyntaxError: unexpected token in scriptThis error appears in the browser console when executing client scripts, UI policies, or catalog client scripts. It also shows in the System Log under System Diagnostics > Log > Application Log when server-side scripts contain syntax errors. The error prevents the script from being parsed and executed by the JavaScript engine.→LDAP import: user record not created after syncThis error appears in the System Log under System Diagnostics > Log > Application Log or in the LDAP Import Status page after an LDAP import operation completes. The import shows as successful but expected user records are missing from the sys_user table.→Large record count warning: query returned excessive rowsThis warning appears in the ServiceNow application log and system diagnostics when a GlideRecord query executes without proper row limits. The error typically occurs during script execution in business rules, scheduled jobs, or background scripts when queries return more records than the system's configured warning threshold.→List view shows no records: expected records not appearingThis issue occurs when navigating to a list view in the ServiceNow interface where records are expected but none are displayed. The error manifests as an empty list with no visible records, even though the underlying table contains data that should be accessible to the current user.→MID Server Java heap space exceeded: out of memoryThis error appears in the MID Server agent.log file when the MID Server JVM runs out of allocated heap memory during processing. It commonly occurs during Discovery, Service Mapping, or other integration operations that handle large datasets or run multiple concurrent probes.→MID Server authentication failed: invalid credentialsThis error appears in the MID Server logs, ECC Queue records, and System Log under System Diagnostics > Log > Application Log. It occurs when a MID Server attempts to authenticate with the ServiceNow instance during startup, heartbeat validation, or when processing ECC queue records.→MID Server down: no available MID Server for this requestThis error appears in the ServiceNow ECC Queue when attempting to execute outbound integrations, discovery jobs, or orchestration workflows that require MID Server communication. The error is typically visible in the ECC Queue records under System Diagnostics > ECC Queue, and may also appear in system logs during automated processes.→Mutual authentication not established for outbound connectionThis error appears in the System Log under System Diagnostics > Log > System Log when ServiceNow attempts to make outbound REST or SOAP calls that require mutual TLS authentication. It typically occurs during integration operations where both client and server certificates must be validated for secure communication.→Node memory high: JVM heap usage approaching limitThis error appears in the System Log (System Diagnostics > Log > Application Log) and the Node Monitor dashboard when a ServiceNow application node's JVM heap memory usage exceeds configured thresholds. The error typically occurs during high system activity or when memory-intensive operations are running.→Notification script error: notification script threw exceptionThis error appears in the System Log under System Diagnostics > Log > Application Log when a notification fails to generate due to a JavaScript exception. The error occurs during notification processing when either the message script or condition script encounters a runtime error, preventing the notification from being created or sent.→OAuth token expired or revoked: re-authentication requiredThis error appears in System Logs (System Diagnostics > Log > System Log) when making outbound REST calls or executing Integration Hub spokes that use OAuth 2.0 authentication. The error typically occurs during REST message execution or spoke activities when the stored OAuth access token is no longer valid and cannot be refreshed.→Orchestration activity timeout: remote activity did not respondThis error appears in Orchestration activity logs and workflow activity states when a ServiceNow Orchestration activity sends a job to a MID Server but receives no response within the configured timeout period. The error is visible in the ECC Queue records, System Log entries, and workflow activity execution details.→Order guide validation failed: inter-variable dependency not satisfiedThis error appears in the browser UI when users attempt to submit an order guide with unfulfilled variable dependencies. The error typically displays as a modal dialog or inline notification on the order guide form, preventing submission until all inter-variable dependency conditions are met.→Outbound SSL handshake failed: certificate validation errorThis error appears in the System Log under System Diagnostics > Log > Application Log when ServiceNow attempts to make outbound HTTPS connections to external systems. It commonly occurs during REST API calls, web service integrations, or when using Business Rules, Script Includes, or scheduled jobs that connect to external endpoints.→Parallel flow branches deadlocked: join never completedThis error appears in the System Log under System Diagnostics > Log > Application Log when parallel workflow branches fail to reach completion, preventing the join activity from executing. The error typically occurs during workflow execution when one or more parallel branches become stuck in a non-terminal state, causing the entire workflow to hang indefinitely.→Plugin activation failed: dependency plugin not installedThis error appears in the System Logs under System Diagnostics > Log > Application Log when attempting to activate a plugin through Plugins application or during automated plugin activation during upgrades. It occurs when ServiceNow detects that a required dependency plugin is not active on the instance before the target plugin can be enabled.→REST API 401 Unauthorized: invalid or missing credentialsThis error appears in REST API responses when making HTTP requests to ServiceNow Table APIs or scripted REST APIs. The error is returned in the HTTP response body and may also appear in the Application Log under System Diagnostics > Logs > Application Log when authentication fails.→REST API 500 Internal Server Error from target endpointThis error appears in ServiceNow system logs, ECC queue records, or integration responses when making outbound REST API calls to external systems. It occurs during REST message executions, scheduled imports, or any integration that calls external REST endpoints when the target server experiences an internal error.→REST API rate limit exceeded: 429 Too Many RequestsThis error appears in the ServiceNow System Log (System Diagnostics > Log > Application Log) or ECC queue when outbound REST integrations exceed external API provider rate limits. It commonly occurs during bulk data synchronizations, scheduled imports, or high-frequency polling operations using REST Message records or scripted REST calls.→REST message connection refused: target host unreachableThis error appears in the ServiceNow System Log under System Diagnostics > Log > Application Log when outbound REST integrations fail. It commonly occurs during scheduled integrations, manual REST message testing, or when using the REST Message form test functionality.→Record not accessible: no read ACL for this recordThis error appears in server-side scripts, business rules, or background scripts when attempting to access fields on a GlideRecord object that was returned by a query but the current user lacks read ACL permissions for that specific record. The error may appear in application logs or script debugger output when field values return null unexpectedly.→Recursion detected: business rule triggered itselfThis error appears in the System Log at System Diagnostics > Log > Application Log when a business rule creates an infinite loop. The error occurs during record operations like insert, update, or delete when ServiceNow's recursion detection prevents a stack overflow by stopping the loop after detecting the same business rule triggering repeatedly.→Related list missing from form: expected related list not visibleThis error typically appears in browser console logs or system application logs when a user accesses a form where an expected related list should be displayed. The error occurs during form rendering when ServiceNow cannot display a configured related list due to access restrictions, configuration issues, or relationship problems.→Requested item stuck in open state: fulfillment not progressingThis error typically appears in the Requested Item (RITM) record when monitoring catalog fulfillment progress or in system notifications. The error indicates that a catalog item request has remained in the Open state without advancing to Work in Progress or other expected states. ServiceNow administrators may also see this in workflow diagnostics or catalog management reports.→Role not found for user: required role missingThis error typically appears in the Application Log under System Diagnostics > Log > Application Log when ACL evaluations fail. It can also surface in browser console logs when UI actions or modules attempt to load but encounter role validation failures during user session activities.→Row count exceeded: import set exceeds maximum row limitThis error appears in the ServiceNow system logs and import progress notifications when attempting to create or load data into an import set table. The error occurs during data import operations through Data Sources, scheduled imports, or REST API calls when the number of rows exceeds the configured system limit.→SLA not attaching to record: SLA definition conditions not metThis error appears in the System Log under System Diagnostics > Log > Application Log when an SLA definition fails to attach to a record despite expectations. It commonly occurs during record creation, updates, or state changes that should trigger SLA attachment. The error may also be visible in SLA diagnostic logs when SLA debugging is enabled.→SMTP connection failed: cannot connect to mail serverThis error appears in the System Log under System Diagnostics > Log > Application Log when ServiceNow attempts to send email notifications. It typically occurs during outbound email processing and can be seen in notification log entries or when testing email configurations.→SOAP fault: server returned a fault responseThis error appears in the System Log under System Diagnostics > Log > Application Log when ServiceNow makes an outbound SOAP web service call. The error occurs when the target web service returns a SOAP fault response instead of a successful response, typically during business rule executions, scheduled jobs, or workflow activities that invoke external systems.→SSO SAML assertion validation failed: signature mismatchThis error appears in the System Log under System Diagnostics > Log > Application Log when users attempt to authenticate via SAML SSO. The error occurs during the SAML assertion validation process when ServiceNow receives a response from the identity provider but cannot verify the digital signature.→Scheduled import not running: import set job inactiveThis error appears in the System Log under System Diagnostics > Log > Application Log when a scheduled data source import fails to execute at its configured interval. The error is typically logged during the scheduled job execution window when ServiceNow attempts to trigger an import set transformation but finds the associated import job is not in an active state.→Scheduled job not executing at configured timeThis error appears in the System Log under System Diagnostics > Logs > System Log when monitoring scheduled job execution. It can also be observed in the Scheduled Jobs list where the Next Run time passes without execution occurring, or when reviewing job history shows missed executions.→Scope not found: application scope does not existThis error appears in the Application Log at System Diagnostics > Logs > Application Logs when executing server-side scripts that reference objects from a missing application scope. It commonly occurs during script execution in Business Rules, Script Includes, or scheduled jobs that attempt cross-scope API calls to deleted or unavailable scoped applications.→Script Include not found: unable to instantiate classThis error appears in browser console logs, system application logs, or script debugger when attempting to instantiate a Script Include using the new operator or calling a static method. The error typically occurs during server-side script execution in Business Rules, Script Actions, or other server-side scripts.→Script aborted: transaction quota exceededThis error appears in the system application log accessible via System Diagnostics > Log > Application Log when server-side scripts exceed platform-imposed resource limits. It commonly occurs during Business Rule execution, Script Include operations, scheduled jobs, or background scripts that consume excessive database transactions, processing time, or memory.→Script execution timed out: exceeded maximum allowed timeThis error appears in the System Log under System Diagnostics > Log > Application Log when server-side scripts exceed the configured transaction quota or script execution timeout. It commonly occurs during business rule execution, scheduled jobs, or background scripts that run too long.→Security constraint violation: operation not permittedThis error appears in the ServiceNow application log, browser developer console, or system diagnostics when server-side security mechanisms block an attempted operation. It typically occurs during record queries, form submissions, or script executions that violate Access Control Lists (ACLs), System Security constraints, or before-query business rule restrictions.→Semaphore wait timeout: request queued too longThis error appears in the Application Log under System Diagnostics > Log > Application Log when a request has waited in the semaphore queue beyond the configured timeout period. It typically occurs during high system load or when long-running transactions occupy all available semaphore slots, preventing new requests from being processed.→Service Portal widget error: widget script threw exceptionThis error appears in the browser console when a Service Portal widget's JavaScript code encounters an unhandled exception during execution. The error typically occurs when loading a Service Portal page or when widget code executes during user interactions, causing the affected widget to render blank or display incorrectly.→Service mapping incomplete: application service missing dependenciesThis error appears in the Service Mapping Discovery Status dashboard and System Log under System Diagnostics > Log > Application Log during Service Mapping pattern execution. It occurs when Service Mapping successfully discovers the primary application service but fails to identify or map one or more dependent configuration items required to complete the service topology.→ServiceNow Store app incompatible with current family releaseThis error appears in the ServiceNow Store interface when attempting to install or update an application from the Store. It typically displays in the application installation dialog or on the application details page within the Store UI. The error may also appear in System Logs during automated app update processes.→Session timeout: your session has expiredThis error appears in the ServiceNow user interface when attempting to perform actions after a session has expired, typically displaying as a modal dialog or redirect to the login page. It can also appear in system logs when automated processes or service accounts encounter token expiration issues during API calls or scheduled jobs.→Slow query detected: database query exceeded performance thresholdThis error appears in the System Log under System Diagnostics > Log > Application Log when a GlideRecord query or database operation takes longer than the configured slow query threshold (typically 3-5 seconds). It commonly occurs during Business Rule execution, Script Include operations, or when processing large data sets in scheduled jobs.→Stack overflow: maximum call stack size exceededThis error appears in the ServiceNow browser console, System Log, or application error messages when JavaScript code enters infinite recursion. It commonly occurs during Business Rule execution, Script Include functions, or client-side scripts when recursive function calls exhaust the JavaScript engine's call stack memory.→Subflow not found: referenced subflow does not existThis error appears in Flow Designer when activating or executing a flow that references a missing subflow. The error is displayed in the Flow Designer interface during flow validation or in the Flow Context record during flow execution. It can also appear in the System Log under Flow Designer execution logs.→Transaction quota exceeded: script consumed too many resourcesThis error appears in the ServiceNow System Log under System Diagnostics > Log > Application Log when a server-side script exceeds resource limits during execution. The error typically occurs during Business Rules, Script Includes, Scheduled Jobs, or Transform Maps when database queries, CPU processing, or external HTTP calls consume too many resources within a single transaction.→Transform map field mapping error: source field missingThis error appears in the System Log under System Diagnostics > Log > Application Log during data import operations when transform maps attempt to process import set records. It occurs when the transform map tries to access a source field that no longer exists in the import set staging table, typically during scheduled imports or manual data loading processes.→TypeError: Cannot call method on undefined objectThis error appears in ServiceNow application logs, browser console, or script debugger when attempting to call a method on an object that is null or undefined. It most commonly occurs in server-side scripts, client scripts, and business rules when working with GlideRecord references or API objects that failed to instantiate properly.→TypeError: undefined is not a functionThis error appears in ServiceNow system logs, browser console, or script debugger when server-side or client-side scripts attempt to call a method on an undefined variable. It commonly occurs in Business Rules, Script Includes, UI Actions, Client Scripts, and Scripted REST APIs during script execution.→UI Builder component error: component failed to renderThis error appears in the browser console when a UI Builder component in Next Experience fails to load or display properly. It typically occurs when loading pages built with UI Builder components, either during initial page load or when component state changes trigger re-rendering.→UI Page not loading: page script error on loadThis error appears when a UI Page fails to render in the ServiceNow interface, typically displayed in the browser as a loading failure or blank page. JavaScript errors related to the UI Page are visible in the browser console, while server-side Jelly template errors appear in the ServiceNow system logs under System Diagnostics > Log > Application Log.→UI action not visible: button or link missing from formThis error typically manifests as missing buttons or links on ServiceNow forms, where expected UI actions do not appear in the form header, right-click context menu, or related links section. The error may appear in browser developer console or be reported by users who cannot see expected form actions.→Update set commit conflict: record modified in both setsThis error appears in the ServiceNow user interface when attempting to commit an update set through System Update Sets > Local Update Sets or System Update Sets > Retrieved Update Sets. The error displays in the commit progress dialog or on the update set form when ServiceNow detects that a record in the current update set conflicts with changes from another update set that was committed after the current set was created.→Upgrade history missing: cannot determine current versionThis error appears in the System Log during upgrade operations or when accessing System Diagnostics > Upgrades > Upgrade History. It typically occurs when ServiceNow cannot read the sys_upgrade_history table to verify the current instance version state before proceeding with an upgrade.→Upgrade skipped customization: local change preserved over base system updateThis message appears in the upgrade progress log and System Upgrade History during ServiceNow instance upgrades when the system detects conflicts between base system updates and local customizations. The message is logged in the upgrade summary report accessible through System Diagnostics > Upgrade History.→Variable set not loading: catalog item variables not appearingThis error occurs when variables from an attached variable set fail to display on a catalog item request form in Service Portal or the platform UI. Users may notice missing form fields or incomplete variable sets when ordering catalog items. The issue may appear during form rendering or be visible in browser console errors.→Version comparison mismatch: update set target version conflictThis error appears in the Application Navigator under System Update Sets > Retrieved Update Sets when attempting to preview or commit an update set that was created on a different ServiceNow version than the target instance. The error is typically displayed in the update set preview results or commit logs, and may also appear in the System Log under System Diagnostics > Logs > System Log.→WSDL import failed: cannot parse web service definitionThis error appears in the ServiceNow application when attempting to import or create SOAP web service integrations through System Web Services > Outbound > SOAP Message or when using the Import WSDL functionality. The error is typically displayed in the browser UI during WSDL import operations and may also appear in application logs under System Diagnostics > Log > Application Log.→Workflow activity fault: activity script threw an exceptionThis error appears in the workflow context log when a Run Script activity within a workflow encounters a JavaScript runtime exception. The error is visible in the workflow context under System Workflow > Live Workflows or when viewing the workflow context record directly. It occurs during workflow execution when the JavaScript code in a Run Script activity fails to execute successfully.→Workflow context cancelled: execution was stoppedThis error appears in the Workflow Context record and System Log when a running workflow is terminated before completion. You'll see it in the workflow execution history, system logs at System Diagnostics > Log > Application Log, and in the workflow context's state field when checking workflow progress.→Workflow stuck in executing state: context not progressingThis error appears in the Workflow Context table (wf_context) when monitoring workflow execution status or in System Diagnostics logs. It occurs when a workflow execution remains in the 'Executing' state for an extended period without transitioning to completion or failure states.→XML export memory error: export exceeded available memoryThis error appears in the application logs at System Diagnostics > Log > Application Log when performing XML exports of large tables or update sets. The error occurs during the export generation phase when the JVM heap memory is exhausted while trying to load and serialize large datasets into XML format.→