Celery integration overview in Flask - Step-by-Step Execution

Concept Flow - Celery integration overview

Start Flask app

↓

Define Celery config

↓

Create Celery instance

↓

Define async task

↓

Call task from Flask route

↓

Task sent to Celery worker

↓

Worker executes task

↓

Result stored or returned

↓

Flask app continues running

This flow shows how a Flask app sets up Celery, defines tasks, sends them to workers, and continues running.

Execution Sample

Flask

from flask import Flask
from celery import Celery

app = Flask(__name__)
celery = Celery(app.name, broker='redis://localhost:6379/0')

@app.route('/start-task')
def start_task():
    result = long_task.delay()
    return f'Task started: {result.id}'

@celery.task
def long_task():
    return 'Task done!'

This code sets up Flask and Celery, defines a long task, and starts it asynchronously from a route.

Execution Table

Step	Action	Evaluation	Result
1	Start Flask app	Flask app instance created	App ready to handle requests
2	Configure Celery	Celery instance created with Redis broker	Celery ready to send tasks
3	Define async task	Task function decorated with @celery.task	Task registered with Celery
4	HTTP GET /start-task	start_task() called	Task long_task sent to Celery worker
5	Celery worker receives task	Worker executes long_task()	Task returns 'Task done!'
6	Result stored	Task result saved in backend	Result available for retrieval
7	Flask route returns	Returns task id string	User sees 'Task started: <id>'
8	End	No more actions	Execution stops here

💡 Execution stops after Flask route returns and Celery worker completes the task asynchronously.

Variable Tracker

Variable	Start	After Step 4	After Step 5	Final
app	Flask instance	Flask instance	Flask instance	Flask instance
celery	Celery instance	Celery instance	Celery instance	Celery instance
result	None	AsyncResult object with task id	AsyncResult object with task result	AsyncResult object with task result
long_task	Function	Function	Function	Function

Key Moments - 3 Insights

Why does the Flask route return immediately before the task finishes?

Because the task is sent asynchronously to Celery workers (see execution_table step 4 and 7), Flask does not wait for task completion.

How does Celery know which broker to use?

The broker URL is set when creating the Celery instance (step 2), telling Celery where to send tasks.

What is the role of the Celery worker?

The worker listens for tasks (step 5), executes them, and stores results independently from Flask.

Visual Quiz - 3 Questions

Look at the execution_table at step 4, what happens when the Flask route is called?

A The task is executed immediately inside Flask

B The task is sent asynchronously to Celery worker

C Flask waits for the task to finish before responding

D The task is ignored

💡 Hint

Check execution_table step 4 and 7 where the task is sent and Flask returns immediately.

According to variable_tracker, what is the value of 'result' after step 5?

A None

B AsyncResult object with task id only

C AsyncResult object with task result 'Task done!'

D String 'Task done!'

💡 Hint

Look at variable_tracker row for 'result' after step 5.

If the broker URL is changed, which step in execution_table is directly affected?

A Step 2 - Configure Celery

B Step 1 - Start Flask app

C Step 4 - HTTP GET /start-task

D Step 5 - Celery worker receives task

💡 Hint

Broker URL is set when creating Celery instance, see step 2.

Concept Snapshot

Celery integration with Flask:
- Create Flask app
- Create Celery instance with broker URL
- Define async tasks with @celery.task
- Call tasks with .delay() from Flask routes
- Celery workers run tasks asynchronously
- Flask returns immediately while tasks run in background

Full Transcript

This visual execution trace shows how to integrate Celery with Flask. First, the Flask app is created and ready to handle requests. Then, a Celery instance is configured with a broker URL, such as Redis. Next, asynchronous tasks are defined using the @celery.task decorator. When a Flask route calls a task using .delay(), the task is sent asynchronously to Celery workers. The Flask route returns immediately with the task id, while the Celery worker executes the task in the background and stores the result. Variables like the Flask app, Celery instance, and task result change state as the program runs. Key points include understanding asynchronous task execution, the role of the broker, and how workers process tasks independently from Flask. The included quiz questions help reinforce these concepts by referencing specific steps and variable states.