From 1044c759924bf0a7a1574e7fd591346c0aa60e5a Mon Sep 17 00:00:00 2001 From: flippedcoder Date: Thu, 12 Feb 2026 14:25:02 -0600 Subject: [PATCH] chore(events): added clarification to ActivityTaskStarted --- docs/references/events.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/references/events.mdx b/docs/references/events.mdx index bf0be5bece..c7ead7c481 100644 --- a/docs/references/events.mdx +++ b/docs/references/events.mdx @@ -251,8 +251,8 @@ This Event type contains Activity inputs, as well as Activity Timeout configurat ### ActivityTaskStarted -This [Event](/workflow-execution/event#event) type indicates that an [Activity Task Execution](/tasks#activity-task-execution) was started. -The SDK Worker picked up the Activity Task and started processing the [Activity](/activities) invocation. +This [Event](/workflow-execution/event#event) type indicates that an [Activity Task Execution](/tasks#activity-task-execution) was started. The SDK Worker picked up the Activity Task and started processing the [Activity](/activities) invocation. `ActivityTaskStarted` is generated by the server when the Task is dispatched to the Worker, not when the Worker starts executing the Task. + Note, however, that this Event is not written to History until the terminal Event (like [ActivityTaskCompleted](#activitytaskcompleted) or [ActivityTaskFailed](#activitytaskfailed)) occurs. | Field | Description |