Skip to content

chore(events): added clarification to ActivityTaskStarted #4211

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
flippedcoder merged 1 commit into from
Feb 12, 2026
Merged

chore(events): added clarification to ActivityTaskStarted #4211

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/references/events.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 |
Expand Down