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.