a0deploy import error keyword replacement not working fails

Not specified by the original author.

TL;DR

The mistralai package changed its import surface across versions, so from mistralai import mistral fails on versions that no longer export that name. Fix it by pinning a known-good version or switching to the current import path (MistralClient / Mistral depending on version), then verify the import in a fresh interpreter.

importerror: cannot import name 'mistral' from 'mistralai' (unknown location)

Use this when

• from mistralai import mistral raises ImportError right after install
• An agent generated code against one SDK version and the env has another
• Upgrading mistralai broke imports that used to work

Not for this skill when

• The import works but API calls fail with auth errors (thats a key problem)
• You get model-not-found or rate-limit errors (thats the API, not the package)
• The traceback names a different package entirely

Steps

1. Check what version is actually installed and what it exports:

pip show mistralai
python -c "import mistralai; print(mistralai.__version__); print([n for n in dir(mistralai) if 'istr' in n.lower()])"

Expected output: the installed version, and a list showing which client names exist. If the list is empty or the version is old, thats your mismatch.

2. Reinstall to a version whose API surface matches your code (1.0 or newer for the v1 import). The v1 rewrite changed the import:

pip install --upgrade mistralai
python -c "from mistralai import Mistral; print('ok')"

Expected output: ok. On pre-1.0 versions the import is from mistralai.client import MistralClient instead.

3. Fix the import line in your code to match the installed version:

from mistralai import Mistral
client = Mistral()

Expected output: no ImportError. If you must stay on an old version, use the legacy import path that version documents.

4. Rule out a shadowed install: a file or folder named mistralai.py / mistralai/ in your working dir wins over site-packages and gives exactly this "unknown location" flavor:

python -c "import mistralai; print(mistralai.__file__)"
ls mistralai*

Expected output: the __file__ path points into site-packages, and the ls finds nothing. If it points at your project dir, rename the local file.

5. Check for a venv mismatch: the package installed for one Python but the code running under another:

which python && python -m pip show mistralai

Expected output: pip show finds the package under the same python you run. If not, install with python -m pip install mistralai.

Variant phrasings

cannot import name 'MistralClient' from 'mistralai'

You are mixing v0 and v1 API surfaces. v1 exports Mistral; v0 exports MistralClient. Pick the one that matches your installed version.

ImportError after pip install mistralai with no version error

Classic venv mismatch or local shadowing (steps 4 and 5). The package is fine, it just isnt on this interpreter's path.

Why it happens

The mistralai SDK went through a breaking v1 rewrite that renamed and moved its client classes. Code (often agent-generated) written against one generation of the API fails to import on the other. The "(unknown location)" suffix specifically means Python found a namespace-ish package with no __init__ exposing the name, often a stale partial install or a shadowing directory.

Edge cases

• Conda and pip both managing the env can leave two copies; pip show and conda list may disagree.
• Some tutorials import from mistralai.models import ...; model class paths changed too, so check the installed version's docs.
• If you see the same error inside Docker, the image layer cached an old version; rebuild without the pip cache.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_PkAzYqUK6F0tMZLQ4EYKLg

Resolved from the public thread: https://vectle.com/posts/pst_PkAzYqUK6F0tMZLQ4EYKLg

Thread query: importerror: cannot import name 'mistral' from 'mistralai' (unknown location)

TL;DR: The mistralai package changed its import surface across versions, so from mistralai import mistral fails on versions that no longer export that name. Fix it by pinning a known-good version or switching to the current import path (MistralClient / Mistral depending on version), then verify the import in a fresh interpreter.

Not specified by the original author.

TL;DR

Don't change code until you've classified the failure from the app's logs: the app owner opens them from the "Manage app" menu (bottom-right of the deployed app). Log lines: ❗️ installer returned a non-zero exit code / ❗️ Error during processing dependencies! Please fix the error and push an update, or try restarting the app.

import streamlit as st

value = st.secrets.get("api_key")
if not value:
    st.error("Missing 'api_key' in app secrets (workspace → app ⋮ → Settings → Secrets).")
    st.stop()

When to use

You are seeing this: Match what you see against the four signatures below. Use this skill when you run into "Classify and fix Streamlit Community Cloud deployment failures".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: pandas 2.2.3. If you are on something much newer or older, the details may have shifted.

Use this when an app runs locally but fails on Streamlit Community Cloud (share.streamlit.io), or when a deployed app that used to work now shows an error page. Don't change code until you've classified the failure from the app's logs: the app owner opens them from the "Manage app" menu (bottom-right of the deployed app). Match what you see against the four signatures below.

1. The four signatures

• A. Dependency failure at build time. Log lines: ❗️ installer returned a non-zero exit code / ❗️ Error during processing dependencies! Please fix the error and push an update, or try restarting the app. The app never starts.

• B. Runtime crash after start. The app builds, then shows "Oh no. Error running app.", or the log says ❗️ Streamlit server consistently failed status checks / ❗️ Please fix the errors, push an update to the git repo, or reboot the app. The traceback in the logs names the real exception.

• C. Resource exhaustion. The app shows "This app has gone over its resource limits." Community Cloud gives each app 1 GB of RAM; exceeding it kills the app, often mid-session.

• D. Secrets/config missing. Works locally, fails on Cloud with a KeyError from st.secrets[...] or a connection error to a private service.

2. Fix A: dependency install failures

• requirements.txt is the supported path; pin versions (pandas==2.2.3) so a fresh solve can't drift. A common failure: a package that installs fine locally fails on Cloud because the local machine had a cached wheel or a system library the Cloud image lacks.

• environment.yml (conda) is a frequent trap: the conda solver can exhaust the 1 GB build memory and get OOM-killed (bash: line 3: 11 Killed ... conda env update), even for packages pip would install fine. Prefer requirements.txt; use conda only if a package truly has no pip wheel.

• Non-Python system libraries (e.g. libgl1 for OpenCV, tesseract-ocr) go in packages.txt at the repo root, one apt package name per line. They are installed with apt before pip runs.

• Set the Python version under Advanced settings at deploy time, and reproduce failures locally with that same version.

3. Fix B: runtime crashes

• Read the traceback in the logs, not the "Oh no" page. It usually names a missing file, a wrong relative path (the working directory on Cloud is the repo root; on your machine you may have run Streamlit from a subfolder), or an unhandled exception in a code path local testing never hit.

• Pushing a fix redeploys automatically. If the app looks stuck after a push, reboot from the ⋮ menu → "Reboot app".

4. Fix C: over resource limits

Rebooting clears it temporarily; the fix is using less memory:

• Don't hold the full raw dataset in memory. Downcast dtypes (object → category, float64 → float32), drop unused columns, aggregate before caching.

• Give caches a ttl so stale entries expire instead of accumulating: @st.cache_data(ttl=3600).

• Load heavy artifacts (model weights) once via @st.cache_resource, not once per session.

• If the dependency install itself gets killed, that's signature A, not C fix the environment, not the code.

5. Fix D: secrets

• Never commit .streamlit/secrets.toml, add it to .gitignore. On Cloud, paste the file's TOML contents into the "Secrets" field under Advanced settings while deploying; for an already-deployed app, go to the workspace, the app's ⋮ menu → Settings → Secrets. The app restarts and picks them up.

• Read secrets in code through indirection, and fail legibly when one is absent:

import streamlit as st

value = st.secrets.get("api_key")
if not value:
    st.error("Missing 'api_key' in app secrets (workspace → app ⋮ → Settings → Secrets).")
    st.stop()

6. Checklist

1. Open the logs (Manage app) and match the signature: dependency (A), runtime (B), resources (C), secrets (D).

2. A → pin requirements.txt, drop conda unless unavoidable, system libs in packages.txt, match the Python version.

3. B → read the traceback; check relative paths and untested code paths.

4. C → reboot is triage; shrink memory (dtypes, ttl, lazy loads) for the cure.

5. D → secrets via app settings, never committed; .gitignore the local file.

Built from Streamlit Community Cloud forum reports (dependency install failures, 'Streamlit server consistently failed status checks', 'This app has gone over its resource limits' with the 1 GB limit, conda solver OOM-kills) and the official Streamlit docs on secrets management for Community Cloud (Advanced settings Secrets field, .streamlit/secrets.toml gitignored, workspace app settings).

Not specified by the original author.

TL;DR

Fix row 14 of the subscriber import file (and scan the whole file for the same fault) before re-importing, because Instatus rejects the import on an invalid email format and will keep stopping at malformed rows. Prove it on one test incident before rolling it to the rest of the affected status page, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.

Instatus subscriber import failed "invalid email format on row 14" error

Use this when

• You see this exact error or symptom: Instatus subscriber import failed "invalid email format on row 14" error.
• The failure is in the status page provider named in the title, and it repeats on the same action rather than happening once and clearing.
• Other items on the same path are working, so the path itself is up and this specific condition is the blocker.

Not for this skill when

• A different error code, message, or tool is involved. Work that error's own skill, because the fix here targets this specific condition.
• The whole service or platform is down. Restore the service first; this skill fixes the named condition, not an outage.
• You cannot identify one affected item to test on. Find one first, because an untested fix rolled out broadly is how this fault gets worse.

Steps

1. Confirm the fault on one test incident first and capture the evidence before changing anything: check the provider's admin console error and activity log for the page, plus the public page as a logged-out visitor sees it, and record the exact error text, the record or host involved, and the time it happened. Verify: you can point to the exact error and the exact item it belongs to, not just the symptom
2. Fix row 14 of the subscriber import file (and scan the whole file for the same fault) before re-importing, because Instatus rejects the import on an invalid email format and will keep stopping at malformed rows. Verify: the specific fault named in the title no longer occurs on that item when you repeat the action that produced it
3. Validate the input against its expected format before the main step consumes it, and report the exact offending record or row instead of failing the whole run. Verify: the guard or check is in place and is visible in the run, log, or configuration you changed
4. Retest end to end: repeat the failed action on a test incident or draft and confirm the public page reflects it without notifying subscribers unintentionally. Verify: the retest completes without the original error and the resulting state matches what a manual check shows
5. Roll the fix out to the rest of the affected status page in the same way, watching the first few for the same error, and note the root cause and the change in the run or incident record. Verify: the remaining items complete without the error recurring, or the ones that still fail are listed individually with their own evidence

Variant phrasings

invalid email format on row 14 fix

The verbatim error or code phrasing for this fault in the status page provider named in the title; the fix is the same one in the steps above.

Instatus subscriber import failed "invalid email format on row 14" error

The full symptom phrasing as it appears in the console, log, or report where this failure surfaces.

how to fix Instatus subscriber import failed "invalid email format

The how-to phrasing for the same fault; start with the TL;DR fix, then work the steps in order.

Compatibility: Atlassian Statuspage, Instatus, Better Stack, Cachet, Status.io, Hund, Freshstatus, Statuspal, UptimeRobot, StatusCake, All Quiet, FireHydrant, Squadcast, xMatters, Grafana Incident and PagerDuty as named in the title.

Why it happens

This fault happens because inputs produced by other systems change format without notice, and a consumer that assumes the old format fails on the first record that differs. In this case the condition is the one named in the title, in the status page provider named in the title: the receiving or acting side reports the failure faithfully, but the underlying state (a record, a setting, a credential, a file, or a mapping) does not match what that action assumes. Fixing the state, as in step 2, clears it; retrying the action without changing the state returns the same error every time, which is why this failure looks stubborn until the state itself is corrected.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_4YzmiWVPHmQfDeHGHibrNA

Resolved from the public thread: https://vectle.com/posts/pst_4YzmiWVPHmQfDeHGHibrNA

Thread query: Instatus subscriber import failed "invalid email format on row 14" error

TL;DR: Fix row 14 of the subscriber import file (and scan the whole file for the same fault) before re-importing, because Instatus rejects the import on an invalid email format and will keep stopping at malformed rows. Prove it on one test incident before rolling it to the rest of the affected status page, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.