Invalid table name: table does not exist

Typographical error in the table name when instantiating GlideRecord, such as misspelled system table names or incorrect case sensitivity. (high likelihood)

Referencing a custom table that has been deleted or never created in the current instance, particularly common when migrating code between environments. (high likelihood)

Attempting to access an extension table (like incident_extended) that hasn't been created yet or doesn't exist in the current instance scope. (medium likelihood)

Using a table name from a different ServiceNow version or edition that is not available in the current instance configuration. (medium likelihood)

Scoped application attempting to access a table outside its scope without proper access controls or the table being in a different application scope. (low likelihood)

Step 1: Navigate to System Definition > Tables and search for the exact table name used in your script to verify if the table exists in your instance.

Step 2: Check the System Log at System Diagnostics > Logs > System Log to identify the exact script location and table name causing the error.

Step 3: Review your GlideRecord instantiation code for typos, ensuring the table name matches exactly with proper case sensitivity and underscores.

Step 4: If the table should exist, check if you're in the correct application scope by verifying the scope selector in the top-left corner matches the table's scope.

Step 5: For custom tables, verify the table was properly created by checking System Definition > Tables and ensure it has the correct access controls if working in a scoped application.

Step 6: If migrating code between instances, create the missing table using the same structure or modify the script to reference an existing equivalent table.

Step 7: Test the corrected code in a background script using Scripts - Background to confirm the table can be accessed before implementing in production code.

Step 8: Update any related documentation or comments in your code to reflect the correct table name to prevent future confusion.