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: specification.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -621,11 +621,11 @@ using and referencing retry definitions see the [Workflow Error Handling](#Workf
621
621
The `keepActive` property allows you to change the default behavior of workflow instances.
622
622
By default, as described in the [Core Concepts](#Core-Concepts) section, a workflow instance is terminated once there are no more
623
623
active execution paths, one of its active paths ends in a "terminate" [end definition](#End-Definition), or when
624
-
its [`execTimeout`](#ExecTimeoutDefinition) time is reached.
624
+
its [`execTimeout`](#ExecTimeout-Definition) time is reached.
625
625
626
626
Setting the `keepActive` property to "true" allows you change this default behavior in that a workflow instance
627
627
created from this workflow definition can only be terminated if one of its active paths ends in a "terminate" [end definition](#End-Definition), or when
628
-
its [`execTimeout`](#ExecTimeoutDefinition) time is reached.
628
+
its [`execTimeout`](#ExecTimeout-Definition) time is reached.
629
629
This allows you to explicitly model workflows where an instance should be kept alive, to collect (event) data for example.
630
630
631
631
You can reference the [specification examples](#Examples) to see the `keepActive` property in action.
0 commit comments