Update functions-timeout-duration.md

[khelhanb-msft]

Submitted via Learn Editor.

[prmerger-automator]

@khelhanb-msft : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit fdef09e:

✅ Validation status: passed

File	Status	Preview URL	Details
includes/functions-timeout-duration.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[learn-build-service-prod]

Learn Build status updates of commit 6ad4cf0:

✅ Validation status: passed

File	Status	Preview URL	Details
includes/functions-timeout-duration.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Jak-MS]

@ggailey777

• Can you review this PR?
• IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[AnnaMHuff]

PR review team emailed author today

[v-ccolin]

I sent an email to the content owner on 01/12/2025.

@MicrosoftDocs/public-repo-pr-review-team

[v-dirichards]

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

[v-dirichards]

@ggailey777

Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

[Copilot]

Pull Request Overview

Clarifies the behavior when an Azure Function execution exceeds the configured timeout.

• Expands description to explain that a timeout causes a process (or worker) restart and terminates running invocations.
• Distinguishes behavior between out-of-process language workers and .NET in-process functions.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

[nitpick] The explanation repeats the concept of process/worker restart and invocation termination twice, which could be made more concise and clearer. Consider restructuring: "If a single execution exceeds this duration, the invocation is aborted and the hosting process/worker is restarted (language worker for out-of-process: Node.js, Python, Java, PowerShell, .NET isolated; function host for .NET in-process), terminating any in-flight invocations."

Suggested change

The timeout duration for functions in a function app is defined by the `functionTimeout` property in the [host.json](../articles/azure-functions/functions-host-json.md#functiontimeout) project file. This property applies specifically to function executions. After the trigger starts function execution, the function needs to return/respond within the timeout duration. If a single execution exceeds this duration, a timeout error will occur, leading to a process restart. In out-of-process languages (such as Node.js, Python, Java, PowerShell, or .NET isolated), the respective language worker process is restarted, thereby terminating any running invocations handled by the process. Similarly, for .NET in-process functions, the host process restarts, also terminating any active invocations. For more information, see [Improve Azure Functions performance and reliability](../articles/azure-functions/performance-reliability.md#make-sure-background-tasks-complete).

The timeout duration for functions in a function app is defined by the `functionTimeout` property in the [host.json](../articles/azure-functions/functions-host-json.md#functiontimeout) project file. This property applies specifically to function executions. After the trigger starts function execution, the function needs to return/respond within the timeout duration. If a single execution exceeds this duration, the invocation is aborted and the hosting process/worker is restarted (language worker for out-of-process: Node.js, Python, Java, PowerShell, .NET isolated; function host for .NET in-process), terminating any in-flight invocations. For more information, see [Improve Azure Functions performance and reliability](../articles/azure-functions/performance-reliability.md#make-sure-background-tasks-complete).

[Copilot]

There is a trailing space at the end of the line; removing trailing whitespace helps keep diffs clean. Please trim the trailing space after the final period.

Suggested change

The timeout duration for functions in a function app is defined by the `functionTimeout` property in the [host.json](../articles/azure-functions/functions-host-json.md#functiontimeout) project file. This property applies specifically to function executions. After the trigger starts function execution, the function needs to return/respond within the timeout duration. If a single execution exceeds this duration, a timeout error will occur, leading to a process restart. In out-of-process languages (such as Node.js, Python, Java, PowerShell, or .NET isolated), the respective language worker process is restarted, thereby terminating any running invocations handled by the process. Similarly, for .NET in-process functions, the host process restarts, also terminating any active invocations. For more information, see [Improve Azure Functions performance and reliability](../articles/azure-functions/performance-reliability.md#make-sure-background-tasks-complete).

The timeout duration for functions in a function app is defined by the `functionTimeout` property in the [host.json](../articles/azure-functions/functions-host-json.md#functiontimeout) project file. This property applies specifically to function executions. After the trigger starts function execution, the function needs to return/respond within the timeout duration. If a single execution exceeds this duration, a timeout error will occur, leading to a process restart. In out-of-process languages (such as Node.js, Python, Java, PowerShell, or .NET isolated), the respective language worker process is restarted, thereby terminating any running invocations handled by the process. Similarly, for .NET in-process functions, the host process restarts, also terminating any active invocations. For more information, see [Improve Azure Functions performance and reliability](../articles/azure-functions/performance-reliability.md#make-sure-background-tasks-complete).