Task is not called

Question

Guys I have an api where your processing takes around 6 hours of execution, so I added a Task.Factory.Startnew with the main processing. So when someone calls, she responds to Statuscode 200 and continues processing "heavy" with the Task:

public override async Task<HttpResponseMessage> Processar(TarefaViewModel tarefa){
        var task = Task.Factory.StartNew(() =>
        {                
            var result = ProcessamentoDe6HorasNoBanco();

            // Chama HttpClient e responde para outra api externa:
            RequestPostStatusGerenciador(result, tarefa.Id, Action.Processar); 

        }, CancellationToken.None, TaskCreationOptions.DenyChildAttach, TaskScheduler.Default);

        return await ResponderAccepted("OK");
    }

However, back and forth the Task is not called I have to recycle the IIS to get back to normal. I suspect it is something related to the IIS Cache. Can anyone shed any light on that? In the properties of Task.Factory.Startnew, such as Taskcreationoptions.Longrunning would make a difference?

Answer 1

I believe that the best option for you would be to integrate the Hangfire to your project.

First install the nuget package

PM> Install-Package Hangfire

In your class Startup add to the method Configuration

GlobalConfiguration.Configuration.UseSqlServerStorage("<connection string or its name>");

app.UseHangfireDashboard();
app.UseHangfireServer();

To view the executed Jobs, you can access the address http://localhost:port/hangfire

To add a Job to Hangfire

BackgroundJob.Enqueue(() => ContabilidadeJobs.GerarLancamentos())

The method is as follows:

[AutomaticRetry(Attempts = 0)]
[LogFailure]
public static async Task GerarLancamentos()
{
    //Processamento pesado
}

I believe that with the use of Hangfire, you will have a better follow-up of the execution of the executed Jobs, including if there have been failures of execution.

In my github, I have a project that used the Hangfire.