Ration

Common troubleshooting

“Not enough credits”

  • Check Hub → Pricing for the organization balance.
  • Remember credits are per organization—switching groups changes which balance applies.
  • MCP does not spend AI credits; if only MCP fails, see Connecting to MCP and rate limits.

Wrong pantry or missing meals

  • Confirm the active group in the hub switcher.
  • Data does not merge across organizations.

Calories look wrong after switching kitchens

  • Pantry and meal plans are always per active group.
  • When cross-kitchen personal diary is on, today’s calorie total can include intake you logged in another kitchen—that is intentional. Rows may show a kitchen name chip. See Macro tracking, goals, and intake.

Cannot invite members or share links

  • Invitations and public share for supply/manifest require Crew Member (and correct role).
  • Limits follow the organization owner’s tier—see Subscription tiers.

Receipt scan stuck or failed

  • Wait for processing; large images or model load can delay results.
  • On failure, credits should refund—refresh balance; if not, contact support with time and org.

URL import “duplicate”

That recipe URL was already imported for this org. Open the existing meal or edit it instead of re-importing.

URL import blocked, partial, or “Listening to the video…”

  • Some publishers block automated downloads. Ration still prefers a saved-link holder so you keep the URL. On web, paste page HTML (or recipe text) into the import dialog and extract (3 credits). On iOS, Ration may reload the page on-device, or you can edit the holder / use a screenshot.
  • Social posts (TikTok / Instagram / YouTube) may show Listening to the video… while spoken-audio transcription runs. A partial skeleton (ingredient names without amounts, or steps only) is a successful import.
  • Holder and skeleton jobs are completed (no refund) — you received a meal to review. Only hard failures (auth, credits, invalid URL) refund. See Import a recipe (URL, social, or photo).

MCP “connection closed” or 401

  • Header must be Authorization: Bearer rtn_live_... (include Bearer ).
  • Key must include the legacy mcp scope or at least one mcp: scope (for example mcp:read). Key must not be revoked.
  • If the client connects but a specific tool fails with “insufficient scope”, the key is missing the narrow scope that tool requires — add the matching mcp:* scope or use legacy mcp.

Rate limited

Slow down requests; see Limits and rate limits. MCP users should space sync_supply_from_selected_meals calls.

If this doc disagrees with the app

Trust the app and contact support with steps to reproduce.