Error Messages

General

When an unexpected condition occurs, you may receive an error message. See the details of each error message below.

ERROR: Transaction is read-only

Amazon Redshift returns this error when connections are set to read-only and variables and temporary tables are being created. Since Redshift creates temporary tables for each subquery, if your query contains subqueries then you will run into this error.

To resolve the error, disable read-only connections for your data source by going to the data source connections settings. Your database will still be protected by Chartio.

You can read more about read-only connections in Chartio’s documentation.

ERROR: canceling statement due to user request

If you see this error message in your query log, it means that the running query has been canceled. This can happen for one of two reasons:

  1. The query was manually canceled, either from the Data Explorer or the Query Log.
  2. The query exceeded the Maximum Query Duration setting for your data source.

Generally, it’s a good idea to keep the Maximum Query Duration set to less than 5 minutes. Any queries which consistently take longer than 5 minutes should be optimized because they tie up database resources and can prevent other charts from loading.

For general tips on optimizing query performance, see our Help Center article.

ERROR: The request could not be satisfied

ERROR: The request could not be satisfied.

If you are trying to export one of your dashboards as a PDF and get an error message like the above, the issue stems from the report timing out.

Generating a report with multiple bar charts with value labels will increase the load time and result in the time out error. Once the value labels are removed, you should be able to download a PDF of the dashboard without any issues.

If this continues to be an issue, you can try improving query performance by limiting queries or separating charts into multiple dashboards to reduce the size and activity on the dashboard. Please take a look at the support documentation on Improving Query Performance for more information.

Row Limit Has Been Reached Error

To improve query performance, Chartio allows you to limit the number of rows that are returned from a database query.

By default, Chartio limits the rows returned for your queries to 1,000 rows.

The warning: “Row limit has been reached and may affect results on Dataset 1” indicates which dataset is not returning full results.

The limit applies to each individual dataset you are querying and the limit can be adjusted individually for each dataset of your analysis.

Warning when row limit has been reached for a dataset

Setting the returned row limit for a dataset


Related General Help Articles

See more