Skip to content

Commit b25069f

Browse files
committed
Link to task spec from progress
1 parent bc12768 commit b25069f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/specification/draft/basic/utilities/progress.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ The receiver **MAY** then send progress notifications containing:
6868
- Send notifications at whatever frequency they deem appropriate
6969
- Omit the total value if unknown
7070

71-
3. For task-augmented requests, the `progressToken` provided in the original request **MUST** continue to be used for progress notifications throughout the task's lifetime, even after the `CreateTaskResult` has been returned. The progress token remains valid and associated with the task until the task reaches a terminal status.
71+
3. For [task-augmented requests](./tasks), the `progressToken` provided in the original request **MUST** continue to be used for progress notifications throughout the task's lifetime, even after the `CreateTaskResult` has been returned. The progress token remains valid and associated with the task until the task reaches a terminal status.
7272
- Progress notifications for tasks **MUST** use the same `progressToken` that was provided in the initial task-augmented request
7373
- Progress notifications for tasks **MUST** stop after the task reaches a terminal status (`completed`, `failed`, or `cancelled`)
7474

0 commit comments

Comments
 (0)