Controlling when the table error handling policy is triggered

A new Number of retries before returning a table error setting has been added to the table error handling settings for replication and landing tasks. Previously, when a table error occurred, the table would be suspended or the task would be stopped (according to the selected error handling action). This sometimes resulted in tables being suspended during the SaaS application maintenance window. With this new option, it is now possible to determine how many times the table should be retried before the table error handling policy is triggered. This option is especially useful if your SaaS application undergoes periodic maintenance, as you can override the default number of retries (3) so that the maintenance can be completed without triggering the table error handling policy.

Table error handling