Function App not waiting for the response from other function app

AJITHKRISHNAMANKENA-7942 0 Reputation points
2025-06-20T05:41:49.98+00:00

I have 2 Azure Function apps. Lets say Function App A and Function App B. Function App A is a .Net 8 and Function App B is Python 3.12. Function App A is having a timer trigger whose functionality is to connect to multiple azure resources and perform required operations. At the last it would be calling this Python Function App B (via Http Post Call) by sending some data for processing and receives the data after processing. Once Function App A receives data from function app B then Function App A saves data into DB and the timer trigger operation is done.

Here the Function App B takes an average of 4 to 5 minutes to process the data received from Function App A. Here the function app A is waiting for 1 Minute 40 Seconds and terminating the execution. Even though the service call to function app B is an await call, Function App A is not waiting for the response from Function App B.

Could you share any suggestions to make the Function App A wait until it receives the response from Function App B?

Your support is highly appreciated.

Thank you in advance😊

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
5,909 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Loknathsatyasaivarma Mahali 2,740 Reputation points Microsoft External Staff Moderator
    2025-06-26T01:24:53.3666667+00:00

    Hello AJITHKRISHNAMANKENA-7942,

    Thank you for your patience and for sharing your feedback on the Q&A community platform. I’m glad to hear that you were able to resolve your issue, and I appreciate you sharing your solution! Your contribution is valuable and can help others in the community facing similar challenges.

    As per the Microsoft Q&A community policy, "The question author cannot accept their own answer. They can only accept answers by others"

    I’m reposting your solution here so you can mark it as accepted if it resolves your query

    Resolution: The root cause of the issue was the default timeout of the HttpClient instance in your .NET Function App A. By default, an HttpClient request will time out after 100 seconds (1 minute and 40 seconds), which precisely matches the behavior you observed. Although your await call was correctly pausing execution, the underlying HTTP task itself was being cancelled by this client-side timeout. By setting the HttpClient.Timeout property to a longer duration (e.g., TimeSpan.FromMinutes(10)), you explicitly instructed the client to wait longer than Function App B's processing time, allowing it to receive the response successfully.

    Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.