Tiingo

# Troubleshooting

## The token and the limits

| What you see | What it means | What to do |
|---|---|---|
| **No key yet** | No token is set | Enter yours in Settings, under API token (the link) |
| **Tiingo refused the token** | Tiingo answered 401 or 403 | Check the token on your Tiingo account's API page, and enter it again |
| **Tiingo's limit was reached** | Too many requests for the plan, here or elsewhere with the same token | Nothing: the plugin waits and tries again |
| Datasets: **Not licensed yet** | No deployment admin has licensed the dataset | Ask a deployment admin to license it on Data sources; the page says so within a minute |

## A fund

| What you see | What it means | What to do |
|---|---|---|
| A fund **not a mutual fund** | Tiingo files the ticker as an ETF or a stock | Its closes come from an equity dataset; remove it from Funds |
| A fund **not found** | Tiingo knows no such ticker | Check the ticker |
| A fund **ambiguous** or **not found** as an instrument | Its ticker found two records, or none to use | Pick its record in the Funds row's Instrument column |
| A day declined, *source silent* | Tiingo has no NAV for it yet | Wait for the night after the business day |

## OpenFIGI

| What you see | What it means | What to do |
|---|---|---|
| **OpenFIGI:** in Connection's last error | OpenFIGI could not be asked, or refused (its limit, say) | Nothing, usually: the fund is resolved by Tiingo's symbol until OpenFIGI answers. With many funds, the deployment's own key in OpenFIGI API key gives higher limits |
| A fund's FIGI reads **None found** | OpenFIGI knows no US mutual fund by that ticker, or more than one | Pick its record in the Funds row's Instrument column |