You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/encyclopedia/workflow-message-passing/sending-messages.mdx
-15Lines changed: 0 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,21 +88,6 @@ Signal-With-Start is a great tool for lazily initializing Workflows. When you se
88
88
89
89
### Sending Updates {#sending-updates}
90
90
91
-
:::note
92
-
93
-
To use the Workflow Update feature in versions prior to v1.25.0, it must be manually enabled.
94
-
95
-
Set the [frontend.enableUpdateWorkflowExecution](https://github.com/temporalio/temporal/blob/main/common/dynamicconfig/constants.go) and [frontend.enableUpdateWorkflowExecutionAsyncAccepted](https://github.com/temporalio/temporal/blob/main/common/dynamicconfig/constants.go) dynamic config values to `true`.
96
-
97
-
For example, with the Temporal CLI, run these commands:
98
-
99
-
```command
100
-
temporal server start-dev --dynamic-config-value frontend.enableUpdateWorkflowExecution=true
101
-
temporal server start-dev --dynamic-config-value frontend.enableUpdateWorkflowExecutionAsyncAccepted=true
102
-
```
103
-
104
-
:::
105
-
106
91
Updates can be sent from a Temporal Client or the Temporal CLI to a Workflow Execution. This call is synchronous and will call into the corresponding Update handler. If you’d rather make an asynchronous request, you should use Signals.
107
92
108
93
In most languages (except Go), you may call `executeUpdate` to complete an Update and get its result.
0 commit comments