[Bug] Week1: Airflow health check cell uses wrong API endpoint for installed version

Author: avibathulaCreated Mar 22, 2026Updated Jun 17, 2026

Environment

  • OS: macOS
  • Docker Desktop: 28.1.1
  • UV: 0.7.x
  • Python: 3.12
  • Airflow version: 2.10.3

Summary

The Week 1 notebook health check cell hits /api/v2/monitor/health, which is an Airflow 3.x endpoint. The container runs Airflow 2.10.3, which does not have this endpoint, causing a 404 and making students think Airflow is not working when it actually is.

Steps to Reproduce

  1. Follow the Week 1 notebook setup
  2. Run the Test Airflow Health cell:
    python
    response = requests.get("http://localhost:8080/api/v2/monitor/health", timeout=5)
  3. Cell prints: ⚠ Airflow returned: 404

Root Cause

The notebook was written targeting Airflow 3.x, where the health endpoint is /api/v2/monitor/health. However the Docker image in compose.yml installs Airflow 2.10.3, which exposes its health endpoint at /health.

Confirmed via:

bash
docker exec rag-airflow airflow version
# 2.10.3

curl http://localhost:8080/health
# {"metadatabase":{"status":"healthy"},"scheduler":{"status":"healthy",...},"triggerer":{"status":"healthy",...}}

Fix

Update the health check cell in week1_setup.ipynb to use the Airflow 2.x endpoint:

python
response = requests.get("http://localhost:8080/health", timeout=5)

Alternatively, if the intent is to use Airflow 3.x, update compose.yml to pin the Airflow image to a 3.x version and align the auth setup accordingly (also see bugtext-airflow1.md which is related).

Source: jamwithai/production-agentic-rag-course