No Cancellation Token on Azure Function Method

In the previous framework, I could pass a cancellation token to an Azure Function Method:

        [FunctionName("my-function")]
        public async Task<IActionResult> MyFunction(
        [HttpTrigger(AuthorizationLevel.Anonymous, "post", Route = null)] HttpRequest req,
        CancellationToken cancellationToken)
        {
             ...
        }

if I try and do that now, an error occurs when calling the method with the cancellation token:

        [FunctionName("my-function")]
        public async Task<HttpResponseData> MyFunction(
            [HttpTrigger(AuthorizationLevel.Anonymous, "post", Route = null)] HttpRequestData req,
            FunctionExecutionContext executionContext),
            CancellationToken cancellationToken)
        {
             ...
        }

This is the error that occurs when calling the method:

[2021-02-05T01:44:09.069Z] System.Private.CoreLib: Exception while executing function: Functions.migrate. System.Private.CoreLib: Result: Failure
Exception: Sequence contains no elements
Stack:    at System.Linq.ThrowHelper.ThrowNoElementsException()
[2021-02-05T01:44:09.070Z]    at Microsoft.Azure.Functions.Worker.Invocation.DefaultFunctionExecutor.ExecuteAsync(FunctionExecutionContext context)
[2021-02-05T01:44:09.071Z]    at Microsoft.Azure.Functions.Worker.FunctionBroker.InvokeAsync(InvocationRequest invocationRequest) in D:\a\1\s\src\DotNetWorker\Broker\FunctionBroker.cs:line 44.

Will support be added back in for the tokens?

[tidusjar]

Is there any update on this?

I’d like to understand the reasoning behind removing the cancellation token, especially in the case of HttpTriggerFunctions where using a CancellationToken makes A LOT of sense.

This is a bit of a deal breaker personally for me as I feel like this is a step backwards and is preventing me from upgrading to net core 5.

[SeanFeldman]

This is why the SDK should provide cancellation token rather than developers come up with their own solutions and recreated the same thing time and time again. From all the things that are being improved with the isolated worker, this feels like a step in the wrong direction. @fabiocav any plans to address this?