This is a basic guide that explains the type of error handling code developers can add to deal with common PowerServer errors.
For example, when the server is restarted, it cleans up the session, which can lead to the 'session not found' error. However, the app cannot handle this gracefully and crashes. Another common issue is when the network connection is lost for a cloud app, but the app assumes there is still a connection and crashes as a result. These are just a few examples. This guide will provide developers with best practices for adding additional error handling code to their PowerServer projects.
Please note that this guide focuses on catching errors and troubleshooting analysis for common runtime problems (such as session, transaction, and network issues) after the application has been successfully deployed. It does not cover deployment-level issues.
