cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
davidbrown100 Regular Visitor
Regular Visitor

Redshift - Data refresh error: The command has been canceled.

As the title says, I am getting a data refresh error.  However this seems intermittent, and once it starts refreshing, it works again until we publish a new report.

The firewall has all traffic on 5389 open, so it isnt a whitelist ip issue between aws and azure.

The error simply says "The command has been canceled. Table: dim_product_type."  The table names at the end vary with randomness.

Is there anywhere else i can look for more information.

1 ACCEPTED SOLUTION

Accepted Solutions
davidbrown100 Regular Visitor
Regular Visitor

Re: Redshift - Data refresh error: The command has been canceled.

OK - I may answer my own question here.  I think that the issue is that the dataset which reports the "failure" may not be the actual dataset causing the failure.

e.g.  If you are refreshing 10 datasets in redshift and 1 has an error, e..g in my case a changed column name.  This error could also prevent other datasets from loading, and the one which gets reported as the "Command has been cancelled" might just be an innocent victim of another issue.

My redshift connector is now refreshing again so I am happy chap..

 

My recommendation is to use the Desktop to refresh, and if this still works, republish the report to ensure that all the schemas are in sync.

1 REPLY 1
davidbrown100 Regular Visitor
Regular Visitor

Re: Redshift - Data refresh error: The command has been canceled.

OK - I may answer my own question here.  I think that the issue is that the dataset which reports the "failure" may not be the actual dataset causing the failure.

e.g.  If you are refreshing 10 datasets in redshift and 1 has an error, e..g in my case a changed column name.  This error could also prevent other datasets from loading, and the one which gets reported as the "Command has been cancelled" might just be an innocent victim of another issue.

My redshift connector is now refreshing again so I am happy chap..

 

My recommendation is to use the Desktop to refresh, and if this still works, republish the report to ensure that all the schemas are in sync.