I have a custom record called "stripe log" having a "level" field. There are 3,057,861 records to update the level from the "scheduled" value to the "handled" value. Out of these, 90,582 records were successfully updated via a standard mass update, but the process stopped, leaving 2,940,843 records still to update. Here are the errors I encountered: INVALID RECORD TYPE. Why do the first 90,582 records work with this record type, while the rest fail?

AI generated answer (using internal Slack threads):

The issue you're encountering, where the first 90,582 records are updated successfully but the rest fail with an INVALID RECORD TYPE error, could be due to a number of reasons. One possibility is that there might be some inconsistency in the data of the remaining records. The first set of records that were updated successfully might have had the correct data format and structure, while the remaining records might have some discrepancies causing the update to fail. Another possibility could be related to the execution context of your script. If the script is running in a scheduled context, there might be some limitations or restrictions that are causing the process to stop after a certain number of records. It's also possible that there might be some concurrent processes or scripts trying to access or modify the same records at the same time, causing conflicts and resulting in the error. To troubleshoot this issue, you could add a try/catch block in your script to capture and log any errors. This could help you identify if there are any specific records causing the issue or if there's a pattern to the failures. Also, you could try to optimize your script by using

record.submitFields

instead of loading the entire record, if you're not already doing so. This method is more efficient and could help improve the performance of your script. Remember to review the data of the remaining records for any inconsistencies or discrepancies. You might need to clean up or standardize the data before attempting the update again. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******