[serverless-offline-sqs] Uncaught exceptions from SQS handler functions terminates nodejs process

[newtechfellas]

Uncaught errors from lambda functions triggered by SQS events terminating serverless process. Is this expected? Is there a configuration to log the error and continue? For example: uncaught errors from lambda functions related to http events (API Gateway), do not kill serverless process. But the same is not true for SQS based events in offline mode.

Example console log:

✖ Uncaught exception
Environment: darwin, node 16.13.1, framework 3.22.0 (local), plugin 6.2.2, SDK 4.3.2
Docs:        docs.serverless.com
Support:     forum.serverless.com
Bugs:        github.com/serverless/serverless/issues

Error: (A custom Error thrown from Lambda)
{ body: '', statusCode: 404, statusType: 'Not Found' }

2 deprecations found: run 'serverless doctor' for more details
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

 *  The terminal process "/bin/zsh '-c', 'yarn run start'" terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it.