Skip to content

Commit 86a78eb

Browse files
authored
Apply suggestions from code review
1 parent fc5c2bc commit 86a78eb

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

articles/azure-functions/dedicated-plan.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,8 +29,7 @@ You pay for function apps in an App Service Plan as you would for other App Serv
2929

3030
When you run your app on an App Service plan, you should enable the **Always on** setting so that your function app runs correctly. On an App Service plan, the Functions runtime goes idle after a few minutes of inactivity. The **Always on** setting is available only on an App Service plan. In other plans, the platform activates function apps automatically. If you choose not to enable **Always on**, you can reactivate an idled app in these ways:
3131

32-
+ Send a request to an HTTP trigger endpoint.
33-
+ Send a request to an `/admin` API endpoint (requires the [master key](function-keys-how-to.md#understand-keys)).
32+
+ Send a request to an HTTP trigger endpoint or any other endpoint on the app. Even a failed request should wake up your app.
3433
+ Acccess your app in the [Azure portal](https://portal.azure.com).
3534

3635
Even with **Always on** enabled, the execution timeout for individual functions is controlled by the `functionTimeout` setting in the [host.json](functions-host-json.md#functiontimeout) project file.

0 commit comments

Comments
 (0)