Hi everyone,
I am seeking some insight into how Canvas LMS handles HTTP errors and how they are reflected in the logs versus the user interface.
We are currently observing the following behavior in our environment:
- Log-only errors: We are seeing 500 (Internal Server Error) and 503 (Service Unavailable) errors recorded in our logs, even though the user does not see any error message on their screen.
- UI errors (502): When the user sees the "Incomplete response received from application" message on their screen, a 502 (Bad Gateway) error is recorded in the logs.
- Data patterns: While the response sizes and latency values vary, we often see identical values for these errors. For example, multiple 500 errors might show a response size of 38 bytes and a latency of 6–7 seconds.
My main question is: Is it standard Canvas LMS behavior to have 500 or 503 errors recorded in the logs without showing an error screen to the end-user? If anyone has experienced similar patterns or knows if this is part of how Canvas handles background processes or retries, I would greatly appreciate your input.
Thank you in advance for your help!
