Skip to content

Commit 3b446aa

Browse files
Small typos in Workflow Error Handling Section (#409)
1 parent d36bcc5 commit 3b446aa

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

specification.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4557,16 +4557,16 @@ execution. Error handling defined in one state cannot be used to handle errors t
45574557
during workflow execution.
45584558

45594559
Errors that may arise during workflow execution that are not explicitly handled within the workflow definition
4560-
should be reported by runtime implementations and halt workflow execution,
4560+
should be reported by runtime implementations and halt workflow execution.
45614561

4562-
Within workflow definitions, errors defined are `domain specific`, meaning they are defined within
4562+
Within workflow definitions, errors defined are **domain specific**, meaning they are defined within
45634563
the actual business domain, rather than their technical (programming-language-specific) description.
45644564

45654565
For example, we can define errors such as "Order not found", or "Item not in inventory", rather than having to
45664566
use terms such as "java.lang.IllegalAccessError", or "response.status == 404", which
45674567
might make little to no sense to our specific problem domain, as well as may not be portable across various runtime implementations.
45684568

4569-
In addition to the domain specific error name, users have the option to also an optional error code
4569+
In addition to the domain specific error name, users have the option to also add an optional error code
45704570
to help runtime implementations with mapping defined errors to concrete underlying technical ones.
45714571

45724572
Runtime implementations must be able to map the error domain specific name (and the optional error code)
@@ -4762,7 +4762,6 @@ In this example we say that if the "Inventory service timeout" error is encount
47624762
which holds the needed retry information. If the error definition does not include a `retryRef` property
47634763
it means that we do not want to perform retries for the defined error.
47644764

4765-
47664765
When referencing a retry strategy in your states error definitions, if the maximum amount of unsuccessful retries is reached,
47674766
the workflow should transition to the next state
47684767
as defined by the error definitions `transition` property. If one of the performed retries is successful,

0 commit comments

Comments
 (0)