flask `app.run` does not match behavior of `flask run` (Fix)

The Fix

Upgrade to version 0.12.3 or later.

Based on closed pallets/flask issue #2590 · PR/commit linked

Production note: Most teams hit this during upgrades or environment changes. Roll out with a canary and smoke critical endpoints (health, OpenAPI/docs) before 100%.

Open PR/Commit

@@ -864,21 +864,34 @@ def run(self, host=None, port=None, debug=None,
             variables from :file:`.env` and :file:`.flaskenv` files.
 
-        .. versionchanged:: 0.10
-           The default port is now picked from the ``SERVER_NAME`` variable.
+            If set, the :envvar:`FLASK_ENV` and :envvar:`FLASK_DEBUG`

fix.md

Option A — Upgrade to fixed release\nUpgrade to version 0.12.3 or later.\nWhen NOT to use: Do not use if it changes public behavior or if the failure cannot be reproduced.\n\n

Why This Fix Works in Production

Trigger: `app.run` does not match behavior of `flask run`
Mechanism: Matches the behavior of `flask run` in `app.run`, enabling threading by default and outputting extra server information.
Why the fix works: Matches the behavior of `flask run` in `app.run`, enabling threading by default and outputting extra server information. (first fixed release: 0.12.3).

Production impact:

If left unfixed, the same config can fail only in production (env differences), causing startup failures or partial feature outages.

Why This Breaks in Prod

Production symptom (often without a traceback): `app.run` does not match behavior of `flask run`

Proof / Evidence

GitHub issue: #2590
Fix PR: https://github.com/pallets/flask/pull/2591
First fixed release: 0.12.3
Reproduced locally: No (not executed)
Last verified: 2026-02-09
Confidence: 0.95
Did this fix it?: Yes (upstream fix exists)
Own content ratio: 0.63

Discussion

High-signal excerpts from the issue thread (symptoms, repros, edge-cases).

Jump to Sources Open on GitHub

“flask run outputs some extra information when starting. Extract this and print it when calling app.run too. app.run runs after the app is loaded and the config created. It can call load_dotenv, which could change the ENV or DEBUG env vars,”

Issue thread · issue description · source

Failure Signature (Search String)

`app.run` does not match behavior of `flask run`
`flask run` enables threading by default, `app.run` does not.

Copy-friendly signature

signature.txt

Failure Signature
-----------------
`app.run` does not match behavior of `flask run`
`flask run` enables threading by default, `app.run` does not.

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
`app.run` does not match behavior of `flask run`
`flask run` enables threading by default, `app.run` does not.

Fix Options (Details)

Option A — Upgrade to fixed release Safe default (recommended)

Upgrade to version 0.12.3 or later.

When NOT to use: Do not use if it changes public behavior or if the failure cannot be reproduced.

Use when you can deploy the upstream fix. It is usually lower-risk than long-lived workarounds.

Fix reference: https://github.com/pallets/flask/pull/2591

First fixed release: 0.12.3

Last verified: 2026-02-09. Validate in your environment.

When NOT to Use This Fix

Do not use if it changes public behavior or if the failure cannot be reproduced.

Did This Fix Work in Your Case?

Quick signal helps us prioritize which fixes to verify and improve.

Prevention

Capture the exact failing error string in logs and tests so you can reproduce via a minimal script.
Pin production dependencies and upgrade only with a reproducible test that hits the failing path.

Version Compatibility Table

Version	Status
0.12.3	Fixed

Related Issues

No related fixes found.

Cluster: flask:configuration-error All hubs All clusters

Related clusters: Data consistency Other Duplicate processing

Sources

We don’t republish the full GitHub discussion text. Use the links above for context.