Updated error handling docs to reflect InvokeAsync() usage. Closes GH…

…-440
JasperFx · Nov 21, 2023 · af7610f · af7610f
1 parent 1a1a1bd
commit af7610f
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 1 deletion.
diff --git a/docs/guide/handlers/error-handling.md b/docs/guide/handlers/error-handling.md
@@ -10,6 +10,12 @@ pause message processing on a single listening endpoint in the case of a high ra
 
 ## Error Handling Rules
 
+::: warning
+When using `IMessageBus.InvokeAsync()` to execute a message inline, only the "Retry" and "Retry With Cooldown" error policies
+are applied to the execution. In other words, Wolverine will attempt to use retries inside the call to `InvokeAsync()` as
+configured.
+:::
+
 Error handling rules in Wolverine are defined by three things:
 
 1. The scope of the rule. Really just per message type or global at this point.

diff --git a/docs/tutorials/mediator.md b/docs/tutorials/mediator.md
@@ -161,7 +161,7 @@ method takes the message passed in, finds the correct execution path for the mes
 executes the correct Wolverine handler(s) as well as any of the registered [Wolverine middleware](/guide/handlers/middleware).
 
 ::: tip
-This execution happens inline, but will use the *RetryNow* error handling capabilities. See [Wolverine's error handling](/guide/handlers/error-handling) for more information.
+This execution happens inline, but will use the "Retry" or "Retry with Cooldown" error handling capabilities. See [Wolverine's error handling](/guide/handlers/error-handling) for more information.
 :::
 
 See also: