You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-functions/errors-diagnostics/diagnostic-events/azfd0011.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.date: 01/24/2024
9
9
10
10
# AZFD0011: The FUNCTIONS_WORKER_RUNTIME setting is required
11
11
12
-
This event occurs when a function app doesn't have the `FUNCTIONS_WORKER_RUNTIME` application setting, which is required.
12
+
This event occurs when a function app doesn't have a value for the `FUNCTIONS_WORKER_RUNTIME` application setting, which is required.
13
13
14
14
|| Value |
15
15
|-|-|
@@ -18,18 +18,20 @@ This event occurs when a function app doesn't have the `FUNCTIONS_WORKER_RUNTIME
18
18
19
19
## Event description
20
20
21
-
The `FUNCTIONS_WORKER_RUNTIME` application setting indicates the language or language stack on which the function app runs, such as `python`. For more information on valid values, see the [`FUNCTIONS_WORKER_RUNTIME`](../../functions-app-settings.md#functions_worker_runtime) reference.
21
+
The `FUNCTIONS_WORKER_RUNTIME` application setting indicates the language or language stack on which the function app runs, such as `python`. For more information on valid values, see the [`FUNCTIONS_WORKER_RUNTIME`][fwr] reference.
22
22
23
-
While not currently required, you should always specify `FUNCTIONS_WORKER_RUNTIME` for your function apps. When you don't have this setting and the Functions host can't determine the correct language or language stack, you might see exceptions or unexpected behaviors.
23
+
You should always specify a valid `FUNCTIONS_WORKER_RUNTIME` for your function apps. When you don't have this setting and the Functions host can't determine the correct language or language stack, you might see performance degradations, exceptions, or unexpected behaviors. To ensure that your application operates as intended, you should explicitly set it in all of your existing function apps and deployment scripts.
24
24
25
-
Because `FUNCTIONS_WORKER_RUNTIME`is likely to become a required setting, you should explicitly set it in all of your existing function apps and deployment scripts to prevent any downtime in the future.
25
+
The value of `FUNCTIONS_WORKER_RUNTIME`should align with the language stack used to create the deployed application payload. If these do not align, you may see the [`AZFD0013`](./azfd0013.md) event.
26
26
27
27
## How to resolve the event
28
28
29
-
In a production application, add `FUNCTIONS_WORKER_RUNTIME` to the [application settings](../../functions-how-to-use-azure-function-app-settings.md#settings).
29
+
In a production application, set [`FUNCTIONS_WORKER_RUNTIME` to a valid value][fwr] in the [application settings](../../functions-how-to-use-azure-function-app-settings.md#settings). The value should align with the language stack used to create the application payload.
30
30
31
-
When running locally in Azure Functions Core Tools, also add `FUNCTIONS_WORKER_RUNTIME` to the [local.settings.json file](../../functions-develop-local.md#local-settings-file).
31
+
When running locally in Azure Functions Core Tools, also set [`FUNCTIONS_WORKER_RUNTIME` to a valid value][fwr] in the [local.settings.json file](../../functions-develop-local.md#local-settings-file). The value should align with the language stack used in the local project.
0 commit comments