AI Research fails at Data Collection with 502 for multiple tickers

[jiaxuan2779096-hue]

Description:
I am using FinRobot Desktop on macOS Apple Silicon.

Basic market data can be loaded successfully, but the full AI Research workflow fails at the Data Collection step for multiple tickers, including AVGO and several other US stocks.

Error message:
"Upstream returned 502"
"Cannot fetch canonical financials"
"all providers failed and no cache is available"

Environment:

• OS: macOS
• Device: Apple Silicon Mac
• FinRobot version: [your version]
• Tested tickers: AVGO, [other tickers]
• Date/time: 2026-08-20, Japan time

Steps to reproduce:

1. Open FinRobot Desktop
2. Enter AVGO
3. Click Analyze
4. Click Run AI Research now
5. The workflow fails at Data Collection after 3 retries

Expected behavior:
The system should collect financial data and generate the AI research report.

Actual behavior:
The Data Collection step fails with a 502 error and the remaining research steps do not start.

Notes:

• FMP, Finnhub and other providers show "Connection OK" in Settings.
• Basic price data works for some tickers.
• API keys have been redacted from the screenshots.

[lrz68]

Thanks for the detailed report — the screenshots let us identify the failure path in desktop-v0.1.0.

AI Research requires canonical financial statements: quarterly income statements, balance sheets, and cash-flow statements. In this release, those can only be supplied by FMP or Yahoo Finance. The reported error means that neither source returned usable financials and no cached financial snapshot was available, so the run stopped instead of generating unsupported numbers.

Finnhub can still provide a current quote without financial statements or daily candle history. That explains why the AVGO price remained visible while the price trend had no history and Data Collection failed.

We also confirmed a defect in the Settings check: FMP “Connection OK” only tests the AAPL company-profile endpoint. It does not test the quarterly statement endpoints used by AI Research. A green check therefore confirms that the key can access the profile endpoint, but not that all research-critical FMP endpoints are available.

The remaining question is why FMP and Yahoo failed on your Mac. Possible causes include FMP plan/quota restrictions, an FMP network error, or Yahoo throttling/connectivity. To distinguish them, please reproduce the failure once and paste the output of:

grep -E "Provider '(fmp|yfinance)'|in cooldown|Data unavailable|Cannot fetch canonical" \
  ~/.finrobot/logs/finrobot.log | tail -n 80

These matching log messages are designed not to include API keys, but please review the output and redact any personal information before posting. Do not share your API keys.

As a temporary workaround:

• If the log shows an FMP plan or quota restriction, confirm that the key can access the stable quarterly income-statement, balance-sheet, and cash-flow endpoints.
• If it shows Yahoo throttling or a network error, retry one ticker after that upstream condition has cleared.

On our side, we have identified three desktop-v0.1.0 issues to address: the incomplete connectivity test, the generic 502 that hides each provider’s failure reason, and retries that treat every provider error as transient.

Sorry about the misleading green check, and thank you for providing enough detail to expose it.

[jiaxuan2779096-hue]

Thanks — I was able to identify the original provider errors.

The root causes appear to be:

1. FMP returns HTTP 402 for AVGO financials, price, and news:
   "Provider 'fmp' failed for AVGO/financials: FMP HTTP 402 during fetch for 'AVGO'"

2. The yfinance fallback is rate-limited:
   "Provider 'yfinance' failed for AVGO/financials: Too Many Requests. Rate limited."

After these failures, both provider circuits enter cooldown, and the local financials endpoint returns 502.

There is also a separate OpenAI TPM rate-limit error during catalyst classification.

For privacy and security reasons, I would prefer not to share the complete log file, as it contains account- and organization-related information. However, I have reviewed it carefully and included the relevant error messages above. Please let me know if any additional specific, non-sensitive log entries would be helpful.

This also confirms that the green FMP connectivity check succeeds on the profile endpoint, while the research-critical endpoints return HTTP 402.

Thank you again for your help.