Errors within API Web App

Question

Errors within API Web App

Logan Elliott 0

We are seeing errors on our API via our Azure App Service Web App.

This has been going on for the past couple of days now and we can't seem to get to the bottom of it. We are making a call to our platform "POST /api/account/GetActiveByName" This is where we are getting a 500 Error and cannot get any further than this. To our knowledge everything is up to date and was working just early last week. We are still able to get some calls through the API and it passes but most of them are now becoming errors.

Bhargavi Naragani 7,940 Reputation points Microsoft External Staff Moderator

2025-07-01T01:12:28.16+00:00
Hi Logan Elliott,

A 500 error generally means there's an unhandled exception on the server side. Here's what could be causing it:

Code-side issues (null references, invalid logic, missing configurations).

Unhandled exceptions during deserialization of the POST request body (malformed JSON, missing fields).

Resource limits (memory, CPU throttling).

Dependency failures (external services, database calls).

Recent platform or package updates that may have silently broken compatibility.

Please follow below steps to resolve the issue:

Enable detailed error messages and application logging:

App Service logs (StdOut, StdErr)

Failed request tracing logs

Detailed error messages Enable diagnostics logging in Azure App Service

Once enabled, you can inspect the logs under: App Service > Monitoring > Log stream. App Service > Monitoring > Diagnose and solve problems

If you're using Application Insights, you can:

Search for failed requests.

Correlate exceptions with dependency failures (like SQL timeouts).

View traces and telemetry. Monitor Azure App Service with Application Insights

Check Web App Health and Quotas - Ensure the app isn't hitting resource limits or experiencing cold starts: Navigate to App Service => Diagnose and Solve Problems => Availability and Performance => Web App Down or Reporting Errors, Review CPU, Memory, and HTTP queue length. Troubleshoot performance issues in Azure App Service

Inspect the Code Path for /GetActiveByName

Wrap logic inside a try-catch block and log exceptions.

Check for null values or missing parameters from the request.

Validate model binding and payload format. Handling Errors in ASP.NET Core Web APIs

Try running the same request locally (with the same payload), if it works locally but not in Azure, compare configuration files (like appsettings.json or environment variables). Re-deploy the app after validating the fix. Deploy ASP.NET Core app to Azure App Service

Hope this helps, if you have any further concerns or queries, please feel free to reach out to us.
Bhargavi Naragani 7,940 Reputation points Microsoft External Staff Moderator

2025-07-03T04:04:17.4466667+00:00

Hi Logan Elliott,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.