> This page location: /docs.md > /docs/development.md > /docs/charts.md > /docs/charts/embed-charts-and-dashboards.md

> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt

# Embedded Error Codes

If an embedded chart or dashboard fails to render, Charts displays an error code in place of the rendered chart or dashboard. Refer to the following table for more information on each error code.

**Note:**

To see a more detailed description of your error, you can open your browser's development console.

| Error Code | Error Cause | More Information |
| --- | --- | --- |
| `-1` | Unknown error. | |
| `2` | Chart not found. | Check the `id` field in the iframe and make sure it matches the `id` in the Embed Chart modal window. |
| `3` | Embedding not enabled. | Check whether embedding is enabled in your chart's or dashboard's Embed Chart or Embed Dashboard modal window. |
| `4` | Embedding not allowed. | Check that embedding is enabled for your chart's or dashboard's backing [data source.](https://www.mongodb.com/docs/charts/manage-data-sources.md#std-label-data-source-embedding) |
| `5` | Invalid payload. | Your application server is not creating a usable [signature.](https://www.mongodb.com/docs/charts/admin-settings.md#std-label-admin-settings) Using verified signatures to authenticate your embedded chart is deprecated. Instead, use an [embedding authentication provider.](https://www.mongodb.com/docs/charts/configure-auth-providers.md#std-label-configure-auth-providers) |
| `6` | Invalid `autoRefresh` value specified. | The `autoRefresh` value must be an integer greater than 0. |
| `7` | [Filter](https://www.mongodb.com/docs/charts/filter-embedded-charts.md#std-label-embed-options-filter) not allowed. | When you filter an embedded chart, the fields used in the filter must be present in the [Allowed filter fields](https://www.mongodb.com/docs/charts/filter-embedded-charts.md#std-label-specify-filter-fields) list. Additionally, filters embedded charts cannot use non-logical operators before a field name (e.g., [`$expr`](https://www.mongodb.com/docs/manual/reference/operator/query/expr.md#mongodb-query-op.-expr), [`$where`](https://www.mongodb.com/docs/manual/reference/operator/query/where.md#mongodb-query-op.-where), or [`$text`](https://www.mongodb.com/docs/manual/reference/operator/query/text.md#mongodb-query-op.-text)). |
| `8` | [Filter](https://www.mongodb.com/docs/charts/filter-embedded-charts.md#std-label-embed-options-filter) not valid. | A `filter` parameter contains an invalid value. |
| `9` | Invalid JWT (JSON Web Token). | Your application's JWT (JSON Web Token) is invalid or malformed. |
| `10` | JWT (JSON Web Token) has no matching providers. | Your application's JWT (JSON Web Token) is not associated with an [Authenticated Embedding Provider.](https://www.mongodb.com/docs/charts/configure-auth-providers.md#std-label-configure-auth-providers) |
| `11` | No authentication providers are configured. | You must configure an [Authenticated Embedding Provider](https://www.mongodb.com/docs/charts/configure-auth-providers.md#std-label-configure-auth-providers) to support your JWT (JSON Web Token). |
| `12` | JWT (JSON Web Token) was issued in the future. | This error can occur if the time on the machine that issued the JWT (JSON Web Token) is more than 5 minutes ahead of the actual time,. This can occur if the machine's time has been manually adjusted. To resolve this error, ensure that the machine issuing the JWT (JSON Web Token) is in sync with the actual time and is set to the correct time zone. |
| `13` | JWT (JSON Web Token) does not have an expiry date. | To use your JWT (JSON Web Token) for authenticated embedding, it must have an expiry date. A JWT (JSON Web Token) that never expires is dangerous because if the token is compromised, someone can always access the data that the token was securing. |
| `14` | JWT (JSON Web Token) is expired. | You need to reissue a JWT (JSON Web Token) with an expiration date in the future. |
| `15` | Token lifetime is greater than 24 hours. | Your token cannot expire more than 24 hours from the time it was created. Refreshing your tokens on a regular basis ensures that the token holder still has expected access rights. |
| `16` | Audience tag on JWT (JSON Web Token) does not match with any provider. | Your JWT (JSON Web Token)'s audience claim must match the audience claim with the token's associated authentication provider. |
| `17` | Injected filter failed to apply. | Your injected filter function failed or returned an illegal result. |
| `18` | Client ID doesn't match provider. | This error occurs for Google authentication providers if the token is valid but was issued for a different application. |
| `19` | Authentication Provider is deprecated. | This error occurs for authentication providers that are deprecated and are no longer supported by MongoDB Atlas Charts. |
