BackgroundTasks

According to this tutorial you can create BackgroundTasks from the route function as follow:

I am using fast API to do predictions of an ml model. When I give a task_id and input it should add it to the background task and return the response accordingly but I am getting Error 500 when I try to do it. After adding task_id_globally it started throwing errors before it worked fine. Error

In an ASP.net core application I spawn background tasks in one request, which can finish by themselves, or be cancelled by a second request. I have the following implementation, but I feel there should be a better way of achieving what I want? Does somebody have some experience with this problem?

I'm getting inconsistent results when using the Background Tasks framework for my application written in SwiftUI. I'm only looking to make quick network requests, so I'm choosing to use BGAppRefreshTask.

Background fetch, and Background Processing are set in Signing & Capabilities. Permitted background task scheduler identifiers have been set. Manually calling it in debugging works fine on a real device but never in production.

I tested both BGAppRefreshTask, and BGProcessingTask. I noticed BGProcessingTask is being called but only when connected to a power supply. I never see any updates from BGAppRefreshTask. I'm not sure if I'm missing something simple.

BGAppRefreshTask hasn't run for FOUR days now since updating this post. BGProcessingTask was run 13 time's overnight but only if my device is charging. Even when setting requiresExternalPower to false.

BGAppRefreshTask run: 0 & BGProcessingTask run: 13

Calling in the debugger using commands here works but it's never run on my device without simulating in the debugger.

I am having a fastapi to do predictions and returing the output as a response but i have implemented input checking where if the user gives unsupported input it returns a Invalid smile but the problem here is the response dictionary is not replaced.

when i do the prediction i got this response

I'm implementing a background app refresh for a watch app. To initiate the background refresh, I call the function below during my model initiation when ContentView is loaded:

Using python 3x on a Mac. I have a FastAPI server with one endpoint. In this endpoint, I want to be able to run some background tasks. After they are completed, make some computation and only then sends an HTTP response.

What I have is the following:

I am currently developing an API that has several endpoints. One of them is to register data in a database, other endpoints are related to simple CRUD endpoints (get data by id, get all data, delete data, etc).

When the register data endpoint is called, a response is almost immediately given back to the API and then a background task is started, where we fetch the data, unzip it if necessary, etc.

We are using FastAPI and async functions for this. What I have noticed, though, is that the API gets blocked by the execution of the background task. This is especially bad when I am uploading a large file to S3 in one go (not in chunks, for which i use async functions), I have to wait for the end of the upload of the full file before another request can get a response (like when requesting the get all data endpoint)).

I am a nube in parallelism and concurrency, but I was expecting the background task not the block the API.

Any ideas on how I could run this long running background task in a way that it won't block new requests to the API? Would celery be best for this?

Mock example:

I have two problems actually. The first is that I am running a background task in my api that is taking an image and predicting on it. . For some reason I cannot store the background task in a variable and return it. I need to do this for the second part of my problem.

API Code: