Skip to main content

Troubleshooting

If you're having issues with your CDB EdgeCompute application, the following section offers helpful tips and troubleshooting suggestions.

HTTP status codes

If your application is correctly configured and works as expected, CDB EdgeCompute will return the expected status code, such as "200 OK."

However, in some exceptional situations, you might get the following status codes. Check the descriptions to understand the root cause.

Status codeDescription
530Internal CDB EdgeCompute error.
531Application has exceeded the allowed memory limit.
532Application has timed out.
533Application has crashed.

Useful resources