RuntimeError: Working outside of application context.
Code used current_app, g, or a Flask extension (like SQLAlchemy) without an active Flask application context.
Seen on:
Python
Meaning
Flask sets up the app context during a request or CLI command. Scripts, background threads, tests and module-level code don’t have one unless you push it.
Common causes
- db.create_all() or queries in a standalone script
- Background thread/Celery task using current_app
- Module-level code accessing current_app
⚡ Quick fix
- Wrap the code: with app.app_context(): ...
- Pass the app object to background workers
- Use Flask CLI commands for maintenance scripts
Detailed fix by platform
Python
- python
with app.app_context(): db.create_all()
How to diagnose
- Where — Request handler, script, thread or test?
- Object — Which object needs the context (db, current_app, g)?
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 2 Oct 2026