Skip to content

Commit 61727da

Browse files
author
Tihomir Surdilovic
authored
Small link fix in spec doc (#253)
Signed-off-by: Tihomir Surdilovic <[email protected]>
1 parent d03035a commit 61727da

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

specification.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -621,11 +621,11 @@ using and referencing retry definitions see the [Workflow Error Handling](#Workf
621621
The `keepActive` property allows you to change the default behavior of workflow instances.
622622
By default, as described in the [Core Concepts](#Core-Concepts) section, a workflow instance is terminated once there are no more
623623
active execution paths, one of its active paths ends in a "terminate" [end definition](#End-Definition), or when
624-
its [`execTimeout`](#ExecTimeout Definition) time is reached.
624+
its [`execTimeout`](#ExecTimeout-Definition) time is reached.
625625

626626
Setting the `keepActive` property to "true" allows you change this default behavior in that a workflow instance
627627
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`](#ExecTimeout Definition) time is reached.
628+
its [`execTimeout`](#ExecTimeout-Definition) time is reached.
629629
This allows you to explicitly model workflows where an instance should be kept alive, to collect (event) data for example.
630630

631631
You can reference the [specification examples](#Examples) to see the `keepActive` property in action.

0 commit comments

Comments
 (0)