Azure datafactory retry and timeout

Shi, Quan 61 Reputation points
2022-06-02T05:38:11.713+00:00

Timeout
Retry
Retry interval (sec)
How do the settings of these three properties affect the pipeline? Are there any recommended settings in principle?

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
11,623 questions
0 comments No comments
{count} votes

Accepted answer
  1. Subashri Vasudevan 11,226 Reputation points
    2022-06-02T09:11:59.17+00:00

    Hi @Shi, Quan ,

    Thanks for posting your query on Microsoft Q&A platform.

    Timeout property mentions the duration of time the pipeline waits for the activities to finish. Once the timeout duration is reached, pipeline throws timeout error. For example for few activities we know it might not take more than 10 hrs. In that case we can set the timeout to be 10 hr.

    Retry mentions no. of times a failed activity can rerun by itself without someone triggering the pipeline. This is helpful when an activity fails due to intermittent connectivity issues and on retry, it might run successfully without manual intervention.

    In case of retry, we need to mention in what interval we need to retry. That's mentioned in retry interval. In the above connectivity example, we can set the timeout interval to be 10 minutes. This means, upon first failure, the pipeline waits for 10 minutes before retrying the activity again.

    Please check this link for understanding. (From MS documentation page)

    Thanks. Please revert for more details.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Samy Abdul 3,376 Reputation points
    2022-06-02T08:31:54.74+00:00

    Hi @Shi, Quan , these setting typically depends on the use-cases. Please go through the below thread for the detail

    explanation.

    https://stackoverflow.com/questions/71998351/how-to-set-a-retry-for-a-pipeline Thanks

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.