Is it possible to configure Qlik Replicate to automatically try unsuspend tables? If not is it possible to unsuspend tabled via the API?

[hr121]

At the moment when a table is suspended due to an error, an alert is sent via email that a particular task has encountered and error and a table has been suspended. At this point a user would go into the Qlik Enterprise Manager and manually unsuspend the task. 

I wanted to ask if there was some kind of automated solution to attempting to unsuspend tasks? 

[Steve_Nguyen]

the suspend of the table because of some error, it is better for user go review the log and see what type of error cause the suspended in the first place.

instead of having API to unsuspend the table.

[Dana_Baldwin · Accepted solution]

@hr121 ,

To add to what Steve said, if we automatically unsuspend tables, there would be data gaps in the target that you may miss. If you unsuspend the table manually there is no chance you will miss this fact.

The other way to handle this is to reload the suspended table. If we did this automatically you may not be aware that the table data won't be complete until the full load is complete. Picking a time to initialize the reload for least impact seems best.

Still, if this is a feature you would like to see in the product, please submit your enhancement request here:

https://community.qlik.com/t5/Ideas/idb-p/qlik-ideas

Thanks,

Dana

[schedde]

I'm looking into automating to unsuspend a table via REST API. After resolving issue that caused the table suspension, does the following API unsuspend the table? 

https://help.qlik.com/en-US/enterprise-manager/November2023/Content/EnterpriseManager/EnterpriseMana...

[PC-1]

If the table is suspended during a reload then Qlik should provide a way of retrying the reload automatically. For example the table reload may have timed out because it was taking so long to apply to the target or it hit a deadlock.

In this case we'd want a retry to be automatic or at least configurable (e.g. retries = 2) within the Task settings

There should be no loss of data if the suspend occurs during a full table reload since Qlik Replicate would just re-read the source data set from scratch at the beginning of each retry ?