Refresh Error - Failed Status

My company has a dataset set up on QuickSight, using multiple tables from RDS which are joined together. We have the dataset on an automatic refresh every hour. We have noticed that occasionally (minimum a few times a day, sometimes more), the refresh fails after attempting at the hour.

This is the refresh error details:

Refresh error details

Ingestion Id
e9cacb3d-e32d-4730-a1d5-c68c5da7534f
Error type:
0 Learn more
Error details:
FATAL: terminating connection due to conflict with recovery Detail: User query might have needed to see row versions that must be removed. Hint: In a moment you should be able to reconnect to the database and repeat your command.

When I go to edit the dataset, I get given this warning message:
7 fields were skipped because they use unsupported data types.

Does anyone know if these unsupported data types are the reason that sometimes the refresh fails?

If this is the problem, I can’t seem to find a way of editing my RDS data sources to exclude these variables, without writing custom SQL data source imports, which then would mess up all of our dashboards and calculated fields that use the variables from the original RDS table that we want to keep.

Any help would be greatly appreciated.

@DannyFowler ,

Possibly this has more to do with your RDS setup . Here is an example ( Troubleshoot the error "canceling statement due to conflict with recovery" in RDS for PostgreSQL | AWS re:Post ) . Check with DB Admin.

When I go to edit the dataset, I get given this warning message:
7 fields were skipped because they use unsupported data types.

It just means there are fields which are unsupported in QuickSight and they will be excluded from the dataset. Will not effect the data refresh.

Kind regards,
Koushik

If the unsupported data types will not effect the data refresh, do you know what else it could be that is causing these refresh issues?
@Koushik_Muthanna

Possibly this has more to do with your RDS setup . Here is an example ( Troubleshoot the error “canceling statement due to conflict with recovery” in RDS for PostgreSQL | AWS re:Post ) . Check with DB Admin.