Row count exceeded: import set exceeds maximum row limit

The import file or data source contains more rows than allowed by the system property 'com.glide.import.max_import_set_size' which defaults to 10,000 rows. (high likelihood)

Multiple concurrent imports to the same import set table are accumulating rows beyond the maximum limit. (medium likelihood)

The import set table already contains data from previous imports and the new data would exceed the total row limit. (medium likelihood)

A custom import script or integration is attempting to insert more records than the system allows in a single import set. (medium likelihood)

The system property has been manually reduced below the current import set size after data was already loaded. (low likelihood)

Step 1: Navigate to System Properties > All Properties and search for 'com.glide.import.max_import_set_size' to check the current maximum row limit.

Step 2: Go to System Import Sets > Administration > Import Sets to identify which import set table is causing the error and count the existing rows.

Step 3: If increasing the limit is appropriate for your instance, modify the 'com.glide.import.max_import_set_size' property to a higher value considering system performance impact.

Step 4: Alternatively, split your import file into smaller batches that stay under the current limit and process them sequentially through separate import operations.

Step 5: Clear any existing data from the import set table by navigating to the specific import set and using the 'Delete All Rows' option if starting fresh.

Step 6: For ongoing large imports, consider implementing a scheduled job that processes data in manageable chunks rather than bulk loading.

Step 7: Test the import with a smaller subset of data first to ensure the process works before importing the full dataset.

Step 8: Monitor system performance during large imports using System Diagnostics > Stats to ensure the increased limit doesn't impact instance performance.