Graceful Shutdown for Triggered Webjob with only NoAutomaticTrigger

.NET Core 2.2 Webjobs SDK 3.0.10

I am trying to figure out a way I can do a graceful shutdown of my triggered webjob when i manually restart app service, or it is automatically restarted/recycled. I have only a single function decorated with [NoAutomaticTrigger] called like this. This is a long running job for many hours, and there are things i would like to do before it is forcibly stopped.

            using (host)
            {
                await host.StartAsync();
                var jobHost = host.Services.GetService<IJobHost>();
                await jobHost.CallAsync(nameof(Functions.ProcessData));
                await host.StopAsync();
            }

here is my function

        [Singleton]
        [FunctionName(nameof(ProcessData))]
        [NoAutomaticTrigger]
        public async Task ProcessData(ILogger logger, CancellationToken cancellationToken)
        {
                cancellationToken.Register(() =>
                {
                    logger.LogInformation("cancelled!");
                    Console.WriteLine("cancelled");
                });

                while (!cancellationToken.IsCancellationRequested)
                {
                    await Task.Delay(1000, cancellationToken).ConfigureAwait(false);
                    logger.LogInformation("waiting");
                }
                logger.LogInformation("escaped");
        }

i monitor the cancellation token, register a function when cancelled, but it doesn’t appear to be working. Function gets stuck in “waiting” loop I’m not sure if this is just not a supported scenario, or I’m doing something wrong. All the documentation around graceful shutdown i see seems to be around continuous webjobs.

[czb182]

No. I put in the code as I thought it should work, hoping that a future library update will make it work. Unfortunately there is not a lot of activity in this repo, so not sure if/when that would happen

[msftbot[bot]]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.