No API response

Question

No API response

Ledgi 0

Our CRM system is integrated with Azure API Management and Azure Intelligence services. Since today, our background job system (using Hangfire) has multiple jobs stuck in "Processing" state because Azure is not responding to API requests.

The API endpoints are either timing out or not returning any response, which is causing critical delays in our data processing and business operations.

We need urgent assistance to identify if there is an issue with the API Management service or any dependent Azure components.

Shireesha Eeraboina 2,825 Reputation points Microsoft External Staff

2025-05-02T10:08:55.57+00:00

Hi Ledgi,

As suggested by Suwarna S Kale please follow a structured troubleshooting approach—check Azure service health, review APIM and Hangfire logs, and try bypassing API Management temporarily. These steps can help identify the root cause.

Also check if any recent changes were made to API policies or backend services. Misconfigurations or updates might be affecting the response. Enable diagnostic logging in APIM to capture more detailed error traces.

To help you better understand, kindly refer to the documentations below:

https://learn.microsoft.com/en-us/troubleshoot/azure/api-mgmt/availability/api-return-blank-response

https://stackoverflow.com/questions/65902597/api-always-returns-200-with-no-data-in-the-response

https://learn.microsoft.com/en-us/troubleshoot/azure/api-mgmt/availability/performance-hit-api-calls#troubleshooting-steps

By following these steps, you can identify and resolve any issues with the API Management service or other Azure components that may be causing delays in your data processing and business operations.
Shireesha Eeraboina 2,825 Reputation points Microsoft External Staff

2025-05-05T04:28:35.4533333+00:00

Hello Ledgi,

Following up to see if you had a chance to review the response above. Please let me know if you have any further questions.
Shireesha Eeraboina 2,825 Reputation points Microsoft External Staff

2025-05-06T04:52:22.8866667+00:00

Hello Ledgi,

I hope you had a chance to review the response below. If there are any updates or if you need further assistance, please feel free to update here.

1 answer

Your answer

Shireesha Eeraboina 2,825 Reputation points Microsoft External Staff

2025-05-02T10:08:55.57+00:00

Hi Ledgi,

As suggested by Suwarna S Kale please follow a structured troubleshooting approach—check Azure service health, review APIM and Hangfire logs, and try bypassing API Management temporarily. These steps can help identify the root cause.

Also check if any recent changes were made to API policies or backend services. Misconfigurations or updates might be affecting the response. Enable diagnostic logging in APIM to capture more detailed error traces.

To help you better understand, kindly refer to the documentations below:

https://learn.microsoft.com/en-us/troubleshoot/azure/api-mgmt/availability/api-return-blank-response

https://stackoverflow.com/questions/65902597/api-always-returns-200-with-no-data-in-the-response

https://learn.microsoft.com/en-us/troubleshoot/azure/api-mgmt/availability/performance-hit-api-calls#troubleshooting-steps

By following these steps, you can identify and resolve any issues with the API Management service or other Azure components that may be causing delays in your data processing and business operations.
Shireesha Eeraboina 2,825 Reputation points Microsoft External Staff

2025-05-05T04:28:35.4533333+00:00

Hello Ledgi,

Following up to see if you had a chance to review the response above. Please let me know if you have any further questions.
Shireesha Eeraboina 2,825 Reputation points Microsoft External Staff

2025-05-06T04:52:22.8866667+00:00

Hello Ledgi,

I hope you had a chance to review the response below. If there are any updates or if you need further assistance, please feel free to update here.

Answer 1

Hello Ledgi,

Thank you for posting your question in the Microsoft Q&A forum.

When critical API integrations fail, a structured diagnostic approach is essential. First, verify Azure service health to rule out platform-wide outages. Examine API Management logs for latency spikes, throttling, or failed requests that could explain timeouts. Directly test endpoints via Postman to isolate whether issues originate from Hangfire or upstream services. Review Hangfire server logs for HTTP timeout exceptions and ensure proper retry policies are configured. Temporarily bypassing API Management can help determine if it's the bottleneck. If manual troubleshooting reveals no clear cause, escalate to Microsoft Support with correlation IDs and request samples. Implementing circuit breakers in Hangfire jobs may prevent future cascading failures during API disruptions.

Temporary Workaround:

Bypass API Management temporarily by calling backend APIs directly (if possible).
Pause new Hangfire jobs to prevent queue buildup while diagnosing.

If the above answer helped, please do not forget to "Accept Answer" as this may help other community members to refer the info if facing a similar issue. Your contribution to the Microsoft Q&A community is highly appreciated.

Share via

No API response

1 answer

Your answer