Skip to content

Commit 0b469d8

Browse files
authored
Update date and fix grammatical error in documentation
Updated the date for the Azure Batch task complete event documentation and corrected a grammatical error in the description of the 'schedulingError' field.
1 parent e352722 commit 0b469d8

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

articles/batch/batch-task-complete-event.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Azure Batch task complete event
33
description: Reference for Batch task complete event. This event is emitted once a task is completed, regardless of the exit code.
44
ms.topic: reference
5-
ms.date: 01/29/2026
5+
ms.date: 02/05/2026
66
# Customer intent: "As a cloud developer, I want to receive task completion events, so that I can monitor task durations, retry counts, and execution details for better performance analysis and troubleshooting."
77
---
88

@@ -88,7 +88,7 @@ ms.date: 01/29/2026
8888
|`retryCount`|Int32|The number of times the Batch service retried the task. The task is retried if it exits with a nonzero exit code, up to the specified MaxTaskRetryCount.|
8989
|`requeueCount`|Int32|The number of times the Batch service requeued the task as the result of a user request.<br /><br /> When nodes are removed from a pool (through resizing or shrinking) or a job is disabled, you can choose to requeue the running tasks on those nodes. This count tracks how many times a task was requeued for these reasons.|
9090
|`result`|String|The task result string, it could be "Success" or "Failure"|
91-
|[`schedulingError`](#schedulingError)|Complex Type|Contain detailed information about error.|
91+
|[`schedulingError`](#schedulingError)|Complex Type|Contains detailed information about error.|
9292

9393
### <a name="schedulingError"></a> schedulingError
9494

0 commit comments

Comments
 (0)