Skip to content

Commit 07a7622

Browse files
Update articles/azure-functions/dotnet-isolated-process-guide.md
Co-authored-by: Matthew Henderson <[email protected]>
1 parent 5535387 commit 07a7622

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-functions/dotnet-isolated-process-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -565,7 +565,7 @@ and those could vary depending on the trigger type being used. Some common reaso
565565
A restart can occur due to worker instance movements, worker instance updates, or scaling.
566566
- Invocations in-flight during a restart event may be retried depending on how they were triggered. Please refer to the [retry documentation](./functions-bindings-error-pages.md#retries) for further information.
567567

568-
For the dotnet-isolated worker, the host we will send the invocation through to the worker _even_ if the cancellation token was cancelled _before_ the host is able to send the invocation request to the worker.
568+
For the isolated worker model, the host we will send the invocation through to the worker _even_ if the cancellation token was cancelled _before_ the host is able to send the invocation request to the worker.
569569

570570
If you do not want pre-cancelled invocations to be sent to the worker, you can add the following property to your host.json file to disable this behaviour.
571571

0 commit comments

Comments
 (0)