Navigation
This documentation refers to the MongoDB Charts service in MongoDB Atlas. Read the on-premises documentation to learn how to use the MongoDB Charts on site.

Embedded Chart Error Codes

If an embedded chart fails to render, Charts displays an error code in place of the rendered chart. 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 that embedding is enabled in your chart’s Embed Chart modal window.
4 Embedding not allowed. Check that embedding is enabled for your chart’s backing data source.
5 Invalid payload.

Your application server is not creating a usable signature.

Note

Using verified signatures to authenticate your embedded chart is deprecated. Instead, use an embedding authentication provider.

6 Invalid autorefresh value specified. The autorefresh value must be an integer greater than 0.
7 Filter not allowed. When you filter an embedded chart, the fields used in the filter must be present in the filter whitelist. Additionally, filters embedded charts cannot use non-logical operators before a field name (e.g., $expr, $where, or $text).
8 Filter not valid. A filter parameter contains an invalid value.
9 Invalid JWT. Your application’s JWT is invalid or malformed.
10 JWT has no matching providers. Your application’s JWT is not associated with an Authenticated Embedding Provider.
11 No authentication providers are configured. You must configure an Authenticated Embedding Provider to support your JWT.
12 JWT was issued in the future.

This error can occur if the time on the machine that issued the JWT 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 is in sync with the actual time and is set to the correct time zone.

13 JWT does not have an expiry date. To use your JWT for authenticated embedding, it must have an expiry date. A JWT that never expires is dangerous because if the token is compromised, someone can always access the data that the token was securing.
14 JWT is expired. You need to reissue a JWT 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 does not match with any provider. Your JWT’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 Realm and Google authentication providers if the token is valid but was issued for a different application.