Repository navigation
Description
Background
Dapr Workflows now supports propagating execution history from a parent workflow to its child workflows and activities. This lets downstream code inspect what happened upstream — useful for chain-of-custody verification, fraud detection, audit, and AI-agent context flow.
Two scopes are exposed:
PropagateLineage— caller's own events plus the full ancestor chainPropagateOwnHistory— caller's events only (a trust boundary; ancestors are dropped)
The Go path is implemented end-to-end. To use this feature from a Java app, this SDK needs the matching API.
Proto surface
From dapr/durabletask-protobuf (PR #38):
history_events.protoTaskScheduledEvent.historyPropagationScope(optional, field 7)ChildWorkflowInstanceCreatedEvent.historyPropagationScope(optional, field 7)- new
PropagatedHistory { repeated HistoryEvent events; HistoryPropagationScope scope; repeated PropagatedHistoryChunk chunks; } - new
PropagatedHistoryChunk { string appId; int32 startEventIndex; int32 eventCount; string instanceId; string workflowName; }
orchestration.proto- new
HistoryPropagationScopeenum:HISTORY_PROPAGATION_SCOPE_NONE = 0,HISTORY_PROPAGATION_SCOPE_OWN_HISTORY = 1,HISTORY_PROPAGATION_SCOPE_LINEAGE = 2
- new
orchestrator_actions.protoScheduleTaskAction.historyPropagationScope(optional, field 6)CreateChildWorkflowAction.historyPropagationScope(optional, field 6)
What needs to happen here
1. Proto regen + plumbing
- Pull the updated
.protofiles fromdapr/durabletask-protobufand regenerate the Java protobuf classes - Plumb the new
historyPropagationScopefield through the schedule-task / create-child-workflow code paths - Surface the received
PropagatedHistoryto the workflow runtime so it can be handed to user code
2. User-facing API to add
Schedule-side (parent workflow author):
WithHistoryPropagation(scope)builder option onCallActivity/CallChildWorkflowPropagateLineage()andPropagateOwnHistory()static factories returning a scope value
Receive-side (child workflow / activity author):
getPropagatedHistory()returningOptional<PropagatedHistory>on bothWorkflowContextandActivityContextPropagatedHistoryclass with:getEvents()— list ofHistoryEventgetScope()— the scope enum valuegetWorkflows()— chunks (each withappId,workflowName,instanceId,startEventIndex,eventCount)getAppIDs()— deduplicated list of app IDs in the chain- convenience filters:
getWorkflowByName(name),getEventsByAppID(appId),getEventsByInstanceID(id),getEventsByWorkflowName(name) - throws
PropagationNotFoundException(or returns emptyOptional) for missing names
3. Example to add
examples/workflow-history-propagation/ mirroring the Go demo: a 3-tier payment workflow (parent → activity → child workflow with PropagateLineage → activity with PropagateOwnHistory). Standalone dapr run mode at minimum; K8s + signing variant a stretch.
4. Tests
At least one test per scope:
- Lineage: parent → child receives parent's events
- OwnHistory: parent → child receives caller's events but NOT grandparent's
AI bootstrap prompt
Paste the following into Claude/Cursor with the dapr/java-sdk repo open:
I'm adding workflow history propagation to dapr/java-sdk. The Go reference implementation is at https://github.com/dapr/go-sdk/tree/main/examples/workflow-history-propagation (PR dapr/go-sdk#823). The proto surface I need to support is in dapr/durabletask-protobuf PR dapr/durabletask-protobuf#38 —
TaskScheduledEvent.historyPropagationScope,ChildWorkflowInstanceCreatedEvent.historyPropagationScope,HistoryPropagationScopeenum,PropagatedHistory+PropagatedHistoryChunkmessages. The durabletask Java is colocated in this repo, so all changes happen here. Tasks: (1) regen the Java protobuf classes from the updated.protofiles and plumb the newhistoryPropagationScopefield through the schedule-task / create-child-workflow paths; (2) add aWithHistoryPropagation(scope)builder option on CallActivity/CallChildWorkflow withPropagateLineage()andPropagateOwnHistory()static factories; (3) addgetPropagatedHistory()returningOptional<PropagatedHistory>on bothWorkflowContextandActivityContext; (4) implementPropagatedHistorywith gettersgetEvents(),getScope(),getWorkflows(),getAppIDs(), plus name/appId/instanceId filters; (5) add anexamples/workflow-history-propagation/matching the Go example shape (parent → activity → child wf with Lineage → activity with OwnHistory); (6) add a unit/integration test covering both scopes. Use Java idioms —Optional, builder pattern, checked exceptions where natural. Don't break existing API.
References
dapr/daprruntime PR: wf history ctx propagation dapr#9810dapr/durabletask-goPR: wf history ctx propagation durabletask-go#85dapr/durabletask-protobufPR: wf history context propagation protos durabletask-protobuf#38dapr/go-sdkreference implementation: Feature workflow history propagation go-sdk#823- Go SDK example:
examples/workflow-history-propagation/
Activity
siri-varma commentedon May 1, 2026
/assign