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: articles/azure-functions/dotnet-isolated-process-guide.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -557,13 +557,14 @@ public async Task HandleCancellationCleanup(
557
557
558
558
#### Scenarios that lead to cancellation token being cancelled
559
559
560
-
The cancellation token is cancelled when any of the following events occur:
560
+
The cancellation token is signaled when the function invocation is canceled. Several reasons could lead to a cancellation,
561
+
and those could vary depending on the trigger type being used. Some common reasons are:
561
562
562
-
1. Client Disconnects: the client that is invoking your function disconnected. This is most likely for HttpTrigger functions.
563
-
2. Function App Restarts: if you or the platform restart your Function App around the same time an invocation is requested. This should not have any impact as when the host starts back up it will retry the request.
564
-
- Restarts could occur due to worker instance movements, worker instance updates, or scaling
563
+
1. Client Disconnect: the client that is invoking your function disconnected. This is most likely for HttpTrigger functions.
564
+
2. Function App Restart: if you, or the platform, restart (or stop) the Function App around the same time an invocation is requested.
565
+
A restart can occur due to worker instance movements, worker instance updates, or scaling.
565
566
566
-
For the dotnet-isolated worker, the host we will send the invocation through to the worker _even_ if the cancellation token was cancelled _before_we get to sending the invocation request to the worker.
567
+
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.
567
568
568
569
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.
569
570
@@ -579,7 +580,7 @@ If you do not want pre-cancelled invocations to be sent to the worker, you can a
579
580
>
580
581
> `Cancellation has been requested. The invocation request with id '{invocationId}' is canceled and will not be sent to the worker`
581
582
>
582
-
> This occurs when the cancellation token is cancelled (via the events defined above) _before_ the host has sent an incoming invocation
583
+
> This occurs when the cancellation token is cancelled (as a result of one of the events described above) _before_ the host has sent an incoming invocation
0 commit comments