Troubleshooting Runtime Errors

Typically, a developer can discover and fix most errors by debugging and testing code during development. However, in some cases, errors can occur at runtime causing custom code execution to terminate. When these errors occur, a developer needs to investigate the cause and fix the code accordingly.

Generally, there are three types of runtime errors:

• Coding Errors: Errors in the developer's code, such as NullPointerException
• Vault Errors: Errors in a service call, such as saving a record without setting a required field value
• Governance Errors: Errors thrown by the System when limits are reached, such as elapsed time or size limits

All three types of errors cause:

• Immediate termination of code execution
• Transaction rollback
• Error message to display to end-users, either in Vault or in an API response

As shown in the message above, Vault directs end-users to an Admin for assistance. The caused by message detail helps developers identify the cause of the error. In some cases, the error message is all a developer needs to fix the error. If a developer needs more information, they can check the Debug Log to further troubleshoot the issue.