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/functions-bindings-warmup.md
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,16 +17,14 @@ This article explains how to work with the warmup trigger in Azure Functions. A
17
17
18
18
The following considerations apply when using a warmup trigger:
19
19
20
+
* There can be only one warmup trigger function per function app, and it can't be invoked after the instance is already running.
21
+
* The name of the function that is the warmup trigger for your app should be `warmup` (case-insensitive).
20
22
* The warmup trigger isn't available to apps running on the [Consumption plan](./consumption-plan.md).
21
23
* The warmup trigger isn't supported on version 1.x of the Functions runtime.
22
24
* Support for the warmup trigger is provided by default in all development environments. You don't have to manually install the package or register the extension.
23
-
* There can be only one warmup trigger function per function app, and it can't be invoked after the instance is already running.
24
25
* The warmup trigger is only called during scale-out operations, not during restarts or other nonscaling startups. Make sure your logic can load all required dependencies without relying on the warmup trigger. Lazy loading is a good pattern to achieve this goal.
25
26
* Dependencies created by warmup trigger should be shared with other functions in your app. To learn more, see [Static clients](manage-connections.md#static-clients).
26
27
* If the [built-in authentication](../app-service/overview-authentication-authorization.md) (also known as Easy Auth) is used, [HTTPS Only](../app-service/configure-ssl-bindings.md#enforce-https) should be enabled for the warmup trigger to get invoked.
The following example shows a [TypeScript function](functions-reference-node.md) with a warmup trigger that runs on each new instance when added to your app:
0 commit comments