Investigating “An Error Occurred” Messages
The “An Error Occurred” message usually indicates an application-level issue rather than a problem with the Frappe Cloud platform. In most cases, the error is caused by a custom app, a failed background job, or an exception generated within your site.
If your site is hosted on a private bench with custom apps, review your application logs before contacting support. The logs often contain the exact error and stack trace needed to identify the issue.
Check Application Logs
If your site is running on a private bench group, you can investigate the error using either the site logs or SSH access.
- Open your site’s Logs page or connect to the bench using SSH.
- Review the web.error.log file for application exceptions and stack traces.
- If you use custom apps, verify that they are not generating runtime errors.
If the Error Appears Occasionally
If the error only appears occasionally as a popup, it is often caused by a failed background job rather than a web request.
In this case, review the following logs:
- Scheduled Job Log
- Error Log
- worker.err.log
These logs can help identify failed scheduled tasks, background workers, or other asynchronous processes that require attention.
Always review the application logs before retrying the failed action. The stack trace in web.error.log or worker.err.log usually provides the fastest way to identify and resolve the underlying issue.
