Error codes

When CloudTables is embedded into your web-application and hits an error, it will show an error message to the end user. This will include an error code along with a message suggesting they get in touch with the system administrator (you!). This page lists those error codes and how to resolve them.

!EXISTS

A table which does not exist or has been deleted has been requested. To resolve this issue:

• If the data set has been deleted, remove the loader code for the data set from your application.
• Check the ID of the data set used in the loader. The data set ID can be viewed in the Data tab of the data set's pages.

DS-LIMIT

When your application contains more data sets than permitted by your current plan (e.g. if downgrading from a purchased package to the free plan) this error message will be shown when trying to access any of the data sets.

The error message will include two numbers (e.g. 14/10). These indicate the number of data sets configured in your application and the number permitted according to your current plan, respectively. To resolve this issue:

• Delete unused data sets to bring the number of data sets back down to the limit. You can delete a data set in its inspector under the data set's Data tab.
• Upgrade to a paid plan in the billing section of this application.

ROW-LIMIT

If your data set contains more records than permitted allowed by your current plan (e.g. if downgrading from a purchased package to the free plan) this error message will be shown when trying to access the data set.

The error message will include two numbers (e.g. 365/250). These indicate the number of records in the data set and the number that can be used according to your current plan, respectively. To resolve this issue:

• Empty the data set of data, which you can do in the data set's inspector of its Data tab.
• Upgrade to a paid plan in the billing section of this application.

INUSE

This error will occur when the token that was used to access the data set is already being used by another client's session. When an access token is used by an end user, it is attached to their browser session. This ensures it cannot be used maliciously by others and protects against CSRF attacks. The result is that tokens cannot be shared between users. To resolve this issue:

• Ensure that a new access token is created for each user. We recommend creating a new token on every page load and allowing old tokens to just expire.

NOACCESS

If an end user attempts to access a data set or property that they have no access rights to, this error message will be shown. To resolve this issue:

• If you are specifying custom roles when generating an access token, ensure that the role(s) used have access to the data set being requested.
• Ensure the API key being used to generate the access token has the role(s) assigned to it to be able to access the data set.
• Check the Security tab for the data set to confirm the role access rights.

NOAPI

This error will occur when using our WordPress plug-in and it is not configured with access keys. To resolve this issue:

• Load your WordPress admin pages
• Access Settings -> CloudTables
• Ensure the correct API keys are filled in for the Editor API Key and Visitor API Key fields.
• API keys can be found in the security section of this application.

NOTOKEN

When embedding a CloudTable into your page, you must provide it with an access token or an API key (if using serverless embedding). The NOTOKEN error will appear if there is no access token or API key given for the embedded script. To resolve this issue:

• Review the embedding documentation
• Also review the documentation for your API client (if using one)
• Get in touch if you are still having problems.

TABLE-ONLY

A view other than a table has been requested by the loader. To resolve this issue:

• Please ensure that the loader URL is in the format https://{your-subdomain}.cloudtables.io/loader/{dataset-id}/table/{styling}.
• This error would happen if anything other than table is specified as the second last part of the URL.