After an uncaught error is thrown, the behavior varies depending on the stage. If the error is thrown during the getInputData stage, the script goes immediately to the summarize stage, and the getInputData stage is not restarted. If an uncaught error is thrown during the map or reduce stage, the default behavior is that the current function invocation ends, even if incomplete, and the map or reduce job moves on to other key/value pairs that require processing. However, the script can be configured so that the map or reduce function is invoked again for the pair that was being processed when the error occurred. You manage the system’s behavior in this case by using the retryCount and exitOnError options.`