One /renew path on a library catalog App Service site returns HTTP…

Question

One /renew path on a library catalog App Service site returns HTTP 500, and the ordinary HTTP log shows only the status code. Which App Service diagnostic should the developer enable for that failing request?

Accepted Answer

Enable failed-request tracing so the platform captures pipeline detail for the failing /renew requests. — Ordinary HTTP logs shout “500!” without showing which pipe burst. Failed-request tracing is the plumber’s camera for that one bad /renew call. You do not need to leave every faucet logging forever to find it.

Answer

Turn on verbose logging for every success and failure on all routes permanently as the only fix.

Answer

Replace App Service with ACI and read docker attach output because failed-request tracing is Windows Server only on-premises.

Answer

Enable only FTP detailed errors and ignore request-tracing XML for HTTP 500 responses.

One /renew path on a library catalog App Service site returns HTTP 500, and the ordinary HTTP log shows only the status code. Which App Service diagnostic should the developer enable for that failing request?

Short Explanation

Full Explanation