@@ -1879,9 +1879,6 @@ async def execute_update(
18791879 This will target the workflow with :py:attr:`run_id` if present. To use a
18801880 different run ID, create a new handle with via :py:meth:`Client.get_workflow_handle`.
18811881
1882- .. warning::
1883- This API is experimental
1884-
18851882 .. warning::
18861883 WorkflowHandles created as a result of :py:meth:`Client.start_workflow` will
18871884 send updates to the latest workflow with the same workflow ID even if it is
@@ -1991,9 +1988,6 @@ async def start_update(
19911988 This will target the workflow with :py:attr:`run_id` if present. To use a
19921989 different run ID, create a new handle with via :py:meth:`Client.get_workflow_handle`.
19931990
1994- .. warning::
1995- This API is experimental
1996-
19971991 .. warning::
19981992 WorkflowHandles created as a result of :py:meth:`Client.start_workflow` will
19991993 send updates to the latest workflow with the same workflow ID even if it is
@@ -2084,9 +2078,6 @@ def get_update_handle(
20842078 Users may prefer the more typesafe :py:meth:`get_update_handle_for`
20852079 which accepts an update definition.
20862080
2087- .. warning::
2088- This API is experimental
2089-
20902081 Args:
20912082 id: Update ID to get a handle to.
20922083 workflow_run_id: Run ID to tie the handle to. If this is not set,
@@ -2116,9 +2107,6 @@ def get_update_handle_for(
21162107
21172108 This is the same as :py:meth:`get_update_handle` but typed.
21182109
2119- .. warning::
2120- This API is experimental
2121-
21222110 Args:
21232111 update: The update method to use for typing the handle.
21242112 id: Update ID to get a handle to.
0 commit comments