Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered

Reply
HamidBee
Power Participant
Power Participant

What’s the Difference Between “Timeout” and “Query Timeout” in the Copy Activity?

Hi All, 

 

I'm working with the Copy Activity in Microsoft Fabric and noticed there are both "Timeout" and "Query Timeout" settings. I understand that "Timeout" generally controls how long the activity itself will run before it stops, but I’m not clear on how "Query Timeout" differs from this.

 

Could someone explain:

 

  1. How each setting impacts the execution of a data copy job?
  2. When it’s appropriate to adjust "Timeout" vs "Query Timeout"?
  3. Whether "Query Timeout" applies only to the data source query, or if it affects the entire data copy operation?

 

Any insights on best practices for setting these timeouts in Copy Activities would be appreciated.

1 ACCEPTED SOLUTION
Anonymous
Not applicable

Hi @HamidBee 

 

1. How each setting impacts the execution of a data copy job?

 

  • Timeout: This setting specifies the maximum duration that the entire Copy Activity is allowed to run. If the activity exceeds this time, it will be forcibly stopped. This is useful for preventing long-running jobs from hanging indefinitely.

  • Query Timeout: This setting specifically controls the maximum time allowed for the execution of the query against the data source. If the query does not complete within this time frame, it will be terminated, but the overall Copy Activity may still continue if other parts are still running.

2. When it’s appropriate to adjust "Timeout" vs "Query Timeout"?

 

  • Adjusting Timeout: You might want to increase the Timeout if you expect the Copy Activity to handle large volumes of data or if the data source is known to be slow. Conversely, if you want to ensure that jobs do not run longer than necessary, you can set a lower Timeout.

  • Adjusting Query Timeout: This is particularly relevant when dealing with complex queries that may take longer to execute. If you notice frequent timeouts during query execution, consider increasing this value. However, if the query is consistently taking too long, it might be worth optimizing the query itself.

 

3. Whether "Query Timeout" applies only to the data source query, or if it affects the entire data copy operation?

 

  • The Query Timeout applies only to the execution of the data source query. It does not affect the entire data copy operation. If the query times out, the Copy Activity may still proceed with other operations unless the overall Timeout is reached.

 

Regards,

Nono Chen

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

View solution in original post

3 REPLIES 3
Anonymous
Not applicable

Hi @HamidBee 

 

1. How each setting impacts the execution of a data copy job?

 

  • Timeout: This setting specifies the maximum duration that the entire Copy Activity is allowed to run. If the activity exceeds this time, it will be forcibly stopped. This is useful for preventing long-running jobs from hanging indefinitely.

  • Query Timeout: This setting specifically controls the maximum time allowed for the execution of the query against the data source. If the query does not complete within this time frame, it will be terminated, but the overall Copy Activity may still continue if other parts are still running.

2. When it’s appropriate to adjust "Timeout" vs "Query Timeout"?

 

  • Adjusting Timeout: You might want to increase the Timeout if you expect the Copy Activity to handle large volumes of data or if the data source is known to be slow. Conversely, if you want to ensure that jobs do not run longer than necessary, you can set a lower Timeout.

  • Adjusting Query Timeout: This is particularly relevant when dealing with complex queries that may take longer to execute. If you notice frequent timeouts during query execution, consider increasing this value. However, if the query is consistently taking too long, it might be worth optimizing the query itself.

 

3. Whether "Query Timeout" applies only to the data source query, or if it affects the entire data copy operation?

 

  • The Query Timeout applies only to the execution of the data source query. It does not affect the entire data copy operation. If the query times out, the Copy Activity may still proceed with other operations unless the overall Timeout is reached.

 

Regards,

Nono Chen

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

Thanks for sharing

Anonymous
Not applicable

Hi @HamidBee 

 

Can you tell me if your problem is solved? If yes, please accept it as solution.

 

Regards,

Nono Chen

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

Helpful resources

Announcements
Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

June FBC25 Carousel

Fabric Monthly Update - June 2025

Check out the June 2025 Fabric update to learn about new features.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.