Fix RuntimeError: RuntimeError: Working outside of application context in Flask

This error occurs when you access Flask objects like current_app, g, or db outside of a request or application context. Flask requires an active application context for these operations. Fix it by wrapping the code in with app.app_context(): or ensuring it runs inside a request handler, CLI command, or test fixture that provides the context.

Reading the Stack Trace

Here's what each line means:

• File "/app/scripts/seed_db.py", line 5, in <module>: A standalone script imports from the app without first creating an application context.
• File "/app/venv/lib/python3.12/site-packages/flask_sqlalchemy/extension.py", line 265, in __getattr__: Flask-SQLAlchemy tries to access the current app to resolve the database connection but no context is active.
• RuntimeError: Working outside of application context.: Werkzeug's context local proxy cannot find an active application context on the current thread.

Common Causes

# scripts/seed_db.py
from app.models import User
from app import db

user = User(name='Admin')
db.session.add(user)
db.session.commit()  # RuntimeError: outside app context

import threading
from flask import current_app

def background_job():
    print(current_app.config['API_KEY'])  # no context

thread = threading.Thread(target=background_job)
thread.start()

def test_user_model():
    user = User(name='Test')  # RuntimeError if no app_context
    assert user.name == 'Test'

The Fix

Create an application instance and use with app.app_context(): to push an application context before accessing Flask-SQLAlchemy or other Flask extensions. This gives Flask the configuration and state it needs to process your operations.

# scripts/seed_db.py
from app.models import User
from app import db

user = User(name='Admin')
db.session.add(user)
db.session.commit()

# scripts/seed_db.py
from app import create_app, db
from app.models import User

app = create_app()
with app.app_context():
    user = User(name='Admin')
    db.session.add(user)
    db.session.commit()
    print(f'Created user: {user.name}')

Testing the Fix

import pytest
from app import create_app, db
from app.models import User

@pytest.fixture
def app():
    app = create_app()
    app.config['TESTING'] = True
    app.config['SQLALCHEMY_DATABASE_URI'] = 'sqlite:///:memory:'
    with app.app_context():
        db.create_all()
        yield app
        db.drop_all()

def test_user_creation_within_context(app):
    with app.app_context():
        user = User(name='Test')
        db.session.add(user)
        db.session.commit()
        assert user.id is not None

def test_current_app_accessible_in_context(app):
    with app.app_context():
        from flask import current_app
        assert current_app.config['TESTING'] is True

Run your tests:

pytest tests/ -v

Pushing Through CI/CD

git checkout -b fix/flask-app-context-script,git add scripts/seed_db.py,git commit -m "fix: wrap script in app_context for Flask context access",git push origin fix/flask-app-context-script

Your CI config should look something like this:

name: CI
on:
  pull_request:
    branches: [main]
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-python@v5
        with:
          python-version: '3.12'
          cache: 'pip'
      - run: pip install -r requirements.txt
      - run: pytest tests/ -v --tb=short
      - run: flake8 app/

The Full Manual Process: 18 Steps

Here's every step you just went through to fix this one bug:

1. Notice the error alert or see it in your monitoring tool
2. Open the error dashboard and read the stack trace
3. Identify the file and line number from the stack trace
4. Open your IDE and navigate to the file
5. Read the surrounding code to understand context
6. Reproduce the error locally
7. Identify the root cause
8. Write the fix
9. Run the test suite locally
10. Fix any failing tests
11. Write new tests covering the edge case
12. Run the full test suite again
13. Create a new git branch
14. Commit and push your changes
15. Open a pull request
16. Wait for code review
17. Merge and deploy to production
18. Monitor production to confirm the error is resolved

Total time: 30-60 minutes. For one bug.

pip install bugstack

import bugstack

bugstack.init(api_key=os.environ["BUGSTACK_API_KEY"])

Deploying the Fix (Manual Path)

1. Run pytest locally to confirm all contexts are properly managed.
2. Open a pull request with the context fix.
3. Wait for CI checks to pass on the PR.
4. Have a teammate review and approve the PR.
5. Merge to main and verify scripts and background tasks work in staging.

Frequently Asked Questions