Skip to content

docs: troubleshooting entry for food-search 503 / Search unavailable #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
KrishP147 merged 1 commit into from
Sep 24, 2026
Merged

docs: troubleshooting entry for food-search 503 / Search unavailable #17

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/08-troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,11 @@ Check:
- Not using `DEMO_KEY` in production
- Haven't exceeded rate limits (1000/hour with personal key, 30/hour with DEMO_KEY)

**Backend: "503 Food database rate-limited" / UI shows "Search unavailable, try again"**

USDA returned 429; `search-food`/`food-details` map it to 503. Wait and retry, or set a personal
`USDA_API_KEY` (functions log a warning when falling back to `DEMO_KEY`). Users can still "Add manually".

**Backend: "Supabase not configured"**

`SUPABASE_URL` and `SUPABASE_SERVICE_ROLE_KEY` are injected automatically by
Expand Down Expand Up @@ -103,6 +108,9 @@ Check:

**Food search returns no results**

"No foods found" means the search succeeded with zero matches; a failed search shows
"Search unavailable, try again" instead (see the 503 entry above).

Solutions:
- Try simpler search terms (e.g., "apple" instead of "green apple")
- USDA database is US-centric
Expand Down
Loading