muFunds
View on GitHub Try in Google Sheets

Troubleshooting

This page aims to consider, comment and solve errors that muFunds users can face.
If you find an unexpected issue, please log them at GitHub.

  • I'm getting wrong data, or data for another listing of the same asset (e.g. multi-listed stocks).

    A same security may trade in different exchanges simultaneously under the same name, ticker and ISIN. In those cases, consider using an asset identifier that uniquely identifies the specific listing you want. For example, search the ISIN/ticker in Morningstar, find the URL of the detail page of the your listing, and extract the Morningstar ID from there:

    Morningstar search for multi-listed assets

  • Error: Unknown option.

    Please check that you introduced a valid option as the first argument of the muFunds function call.

  • Error: Asset identifier is empty.

    Please check that you introduced an asset identifier (string) as the second argument of the muFunds function.

  • Error: Unknown data source.

    Please check the Usage and examples and Compatibility list documentation pages to verify that the data source is compatible with muFunds. Remember that, if you want to obtain data from Google Finance, you should use the Google Finance function included in Google Sheets instead.

  • Error: Asset not found.

    Please check the Compatibility list documentation pages to verify that the asset is compatible with the data source you have chosen, as well as the identifier you have used for it.

  • Error: Requested data is not available for this asset from this data source. Please try a different source.

    Some data sources do not offer all the data options that are possible to call via muFunds. In this case, consider using an alternative data source for your same asset, as sometimes more than one source is compatible at the same time.

  • Error: Exceeded maximum execution time.

    This is not a muFunds' error itself, but Google Sheets complaining because the function is taking too much time. This can happen because Morningstar is responding slowly in that moment, or because many function calls are being performed at the same time (e.g. when you open a spreadsheet with many cells using muFunds). In the latter case, try reducing the number of cells using the function or call muFunds asynchronously, with a time-based trigger.