How Useful is the Retry Setting in Fabric Pipelines?

Hi HamidBee ,

First of all I think you're right that if an activity fails due to a configuration or setup error, simply retrying it won't solve the underlying problem.

However, setting up retries for activities in the fabric pipeline can still be beneficial in several situations:

1. Sometimes, failures occur due to temporary issues like network glitches, service unavailability, or timeouts. In such cases, a retry can help the activity succeed without manual intervention.

2. If the failure is due to resource contention (e.g., database locks or high CPU usage), a retry after a short delay might succeed when the resources become available.

3. Activities that depend on external systems or services might fail if those systems are temporarily down. Retries can help in such cases by giving those systems time to recover.

4. In distributed systems, retries can help balance the load by attempting the activity on a different node or server. 

Best Regards

Yilong Zhou

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.