Large record count warning: query returned excessive rows

GlideRecord query executed without setLimit() method on tables with large datasets, causing memory consumption warnings when row count exceeds the glide.db.max_view_records system property threshold. (high likelihood)

Broad query conditions using addQuery() with wildcards or generic filters that match significantly more records than expected, particularly on high-volume tables like sys_audit or sys_journal_field. (high likelihood)

Missing or ineffective query conditions in GlideRecord scripts, resulting in table scans that return entire table contents rather than filtered result sets. (medium likelihood)

Scheduled jobs or background scripts processing large data sets without implementing proper pagination logic, causing single queries to load excessive records into server memory. (medium likelihood)

Integration scripts or data import processes attempting to query large reference tables without appropriate filtering or chunking mechanisms in place. (low likelihood)

Step 1: Check System Diagnostics > Log > Application Log to identify the specific script and line number generating the large record count warning.

Step 2: Examine the problematic GlideRecord query in the identified script and verify current query conditions using addQuery() methods to ensure they are sufficiently restrictive.

Step 3: Add setLimit() method to the GlideRecord query with an appropriate maximum row count, typically setLimit(1000) or less depending on processing requirements.

Step 4: Implement pagination logic using setLimit() combined with query offset techniques or iterative processing to handle large datasets in manageable chunks.

Step 5: Review and optimize query conditions by adding more specific filters, date ranges, or status conditions to reduce the total number of matching records.

Step 6: Test the modified query in a background script or fix script environment to verify it returns an acceptable number of records without triggering warnings.

Step 7: Monitor the System Log after deployment to confirm the large record count warnings no longer appear for the modified queries.

Step 8: Document the pagination approach and query limits for future maintenance and similar implementations across the instance.