Skip to content

Commit 9a0dc75

Browse files
authored
Merge pull request #291368 from MicrosoftDocs/main
12/4 11:00 AM IST Publish
2 parents 56eebe0 + 4ce68c6 commit 9a0dc75

File tree

106 files changed

+257
-499
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

106 files changed

+257
-499
lines changed

articles/api-management/v2-service-tiers-overview.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -72,6 +72,7 @@ The following API Management capabilities are currently unavailable in the v2 ti
7272

7373
**Infrastructure and networking**
7474
* Multi-region deployment
75+
* Availability zone support
7576
* Multiple custom domain names
7677
* Capacity metric - *replaced by CPU Percentage of Gateway and Memory Percentage of Gateway metrics*
7778
* Built-in analytics - *replaced by Azure Monitor-based dashboard*

articles/azure-functions/durable/durable-functions-entities.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -451,10 +451,10 @@ public static async Task<HttpResponseData> Run(
451451

452452
if (entity is null)
453453
{
454-
return request.CreateResponse(HttpStatusCode.NotFound);
454+
return req.CreateResponse(HttpStatusCode.NotFound);
455455
}
456456

457-
HttpResponseData response = request.CreateResponse(HttpStatusCode.OK);
457+
HttpResponseData response = req.CreateResponse(HttpStatusCode.OK);
458458
await response.WriteAsJsonAsync(entity);
459459

460460
return response;

articles/azure-functions/functions-bindings-timer.md

Lines changed: 27 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -61,6 +61,7 @@ public static void Run([TimerTrigger("0 */5 * * * *")]TimerInfo myTimer, ILogger
6161
---
6262

6363
::: zone-end
64+
6465
::: zone pivot="programming-language-java"
6566

6667
The following example function triggers and executes every five minutes. The `@TimerTrigger` annotation on the function defines the schedule using the same string format as [CRON expressions](https://en.wikipedia.org/wiki/Cron#CRON_expression).
@@ -76,7 +77,8 @@ public void keepAlive(
7677
}
7778
```
7879

79-
::: zone-end
80+
::: zone-end
81+
8082
::: zone pivot="programming-language-python"
8183

8284
The following example shows a timer trigger binding and function code that uses the binding, where an instance representing the timer is passed to the function. The function writes a log indicating whether this function invocation is due to a missed schedule occurrence. The example depends on whether you use the [v1 or v2 Python programming model](functions-reference-python.md).
@@ -135,7 +137,8 @@ def main(mytimer: func.TimerRequest) -> None:
135137

136138
---
137139

138-
::: zone-end
140+
::: zone-end
141+
139142
::: zone pivot="programming-language-typescript"
140143

141144
The following example shows a timer trigger [TypeScript function](functions-reference-node.md?tabs=typescript).
@@ -150,7 +153,8 @@ TypeScript samples are not documented for model v3.
150153

151154
---
152155

153-
::: zone-end
156+
::: zone-end
157+
154158
::: zone pivot="programming-language-javascript"
155159

156160
The following example shows a timer trigger [JavaScript function](functions-reference-node.md).
@@ -188,7 +192,8 @@ module.exports = async function (context, myTimer) {
188192

189193
---
190194

191-
::: zone-end
195+
::: zone-end
196+
192197
::: zone pivot="programming-language-powershell"
193198

194199
Here's the binding data in the *function.json* file:
@@ -220,7 +225,8 @@ if ($myTimer.IsPastDue) {
220225
Write-Host "PowerShell timer trigger function ran! TIME: $currentUTCtime"
221226
```
222227

223-
::: zone-end
228+
::: zone-end
229+
224230
::: zone pivot="programming-language-csharp"
225231
## Attributes
226232

@@ -244,7 +250,7 @@ Write-Host "PowerShell timer trigger function ran! TIME: $currentU
244250

245251
---
246252

247-
::: zone-end
253+
::: zone-end
248254

249255
::: zone pivot="programming-language-python"
250256
## Decorators
@@ -261,6 +267,7 @@ For Python v2 functions defined using a decorator, the following properties on t
261267
| `use_monitor` | Set to `true` or `false` to indicate whether the schedule should be monitored. Schedule monitoring persists schedule occurrences to aid in ensuring the schedule is maintained correctly even when function app instances restart. If not set explicitly, the default is `true` for schedules that have a recurrence interval greater than or equal to 1 minute. For schedules that trigger more than once per minute, the default is `false`. |
262268

263269
For Python functions defined by using *function.json*, see the [Configuration](#configuration) section.
270+
264271
::: zone-end
265272

266273
::: zone pivot="programming-language-java"
@@ -272,7 +279,8 @@ The `@TimerTrigger` annotation on the function defines the `schedule` using the
272279
+ [name](/java/api/com.microsoft.azure.functions.annotation.timertrigger.name)
273280
+ [schedule](/java/api/com.microsoft.azure.functions.annotation.timertrigger.schedule)
274281

275-
::: zone-end
282+
::: zone-end
283+
276284
::: zone pivot="programming-language-javascript,programming-language-typescript,programming-language-powershell,programming-language-python"
277285

278286
## Configuration
@@ -309,7 +317,8 @@ The following table explains the binding configuration properties that you set i
309317

310318
---
311319

312-
::: zone-end
320+
::: zone-end
321+
313322
::: zone pivot="programming-language-powershell,programming-language-python"
314323

315324

@@ -326,7 +335,7 @@ The following table explains the binding configuration properties that you set i
326335

327336
<!--The following Include and Caution are from the original file and I wasn't sure if these need to be here-->
328337

329-
::: zone-end
338+
::: zone-end
330339

331340
[!INCLUDE [app settings to local.settings.json](../../includes/functions-app-settings-local.md)]
332341

@@ -340,6 +349,7 @@ See the [Example section](#example) for complete examples.
340349
When a timer trigger function is invoked, a timer object is passed into the function. The following JSON is an example representation of the timer object.
341350

342351
::: zone pivot="programming-language-csharp,programming-language-java,programming-language-powershell,programming-language-python"
352+
343353
```json
344354
{
345355
"Schedule":{
@@ -353,7 +363,8 @@ When a timer trigger function is invoked, a timer object is passed into the func
353363
"IsPastDue":false
354364
}
355365
```
356-
::: zone-end
366+
::: zone-end
367+
357368
::: zone pivot="programming-language-javascript,programming-language-typescript"
358369
```json
359370
{
@@ -368,7 +379,7 @@ When a timer trigger function is invoked, a timer object is passed into the func
368379
"isPastDue":false
369380
}
370381
```
371-
::: zone-end
382+
::: zone-end
372383

373384
The `isPastDue` property is `true` when the current function invocation is later than scheduled. For example, a function app restart might cause an invocation to be missed.
374385

@@ -410,15 +421,15 @@ Here are some examples of NCRONTAB expressions you can use for the timer trigger
410421
411422
#### NCRONTAB time zones
412423

413-
The numbers in a NCRONTAB expression refer to a time and date, not a time span. For example, a 5 in the `hour` field refers to 5:00 AM, not every 5 hours.
424+
The numbers in an NCRONTAB expression refer to a time and date, not a time span. For example, a 5 in the `hour` field refers to 5:00 AM, not every 5 hours.
414425

415426
[!INCLUDE [functions-timezone](../../includes/functions-timezone.md)]
416427

417428
### TimeSpan
418429

419430
A `TimeSpan` can be used only for a function app that runs on an App Service Plan.
420431

421-
Unlike a NCRONTAB expression, a `TimeSpan` value specifies the time interval between each function invocation. When a function completes after running longer than the specified interval, the timer immediately invokes the function again.
432+
Unlike an NCRONTAB expression, a `TimeSpan` value specifies the time interval between each function invocation. When a function completes after running longer than the specified interval, the timer immediately invokes the function again.
422433

423434
Expressed as a string, the `TimeSpan` format is `hh:mm:ss` when `hh` is less than 24. When the first two digits are 24 or greater, the format is `dd:hh:mm`. Here are some examples:
424435

@@ -464,6 +475,9 @@ Please refer to [manually run a non HTTP-triggered function](./functions-manuall
464475

465476
For information about what to do when the timer trigger doesn't work as expected, see [Investigating and reporting issues with timer triggered functions not firing](https://github.com/Azure/azure-functions-host/wiki/Investigating-and-reporting-issues-with-timer-triggered-functions-not-firing).
466477

478+
## Connections
479+
480+
Timer triggers have an implicit dependency on blob storage, except when run locally through the Azure Functions Core Tools. The system uses blob storage to coordinate across multiple instances [when the app scales out](#scale-out). It accesses blob storage using the host storage (`AzureWebJobsStorage`) connection. If you configure the host storage to use an [identity-based connection](./functions-reference.md#connecting-to-host-storage-with-an-identity), the identity should have the [Storage Blob Data Owner](../role-based-access-control/built-in-roles.md#storage-blob-data-owner) role, which is the default requirement for host storage.
467481

468482
## Next steps
469483

64.7 KB
Loading
119 KB
Loading
Loading
131 KB
Loading
158 KB
Loading
204 KB
Loading
238 KB
Loading

0 commit comments

Comments
 (0)