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

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
mlord
New Member

Data Flow - IR TTL setting

Hello, we are facing an issue with a data flow performance issue and we would like to try to set the Time To Live setting to 10 min, since we have sequential data flows pulling data from an external API.  However, it seems we cannot set TTL in the JSON on an AutoResolveIntegrationRuntime IR, but yet we cannot use a self-hosted IR in a data flow, where the TTL can be set.  This feels like a vicious circle.  What am I missing?

 

Thank you,

Melissa

1 ACCEPTED SOLUTION
v-sdhruv
Community Support
Community Support

Hi @mlord ,

AutoResolveIntegrationRuntime does not allow TTL configuration directly in JSON or UI. This IR is managed by Microsoft and dynamically resolves to the best region, but lacks customization options like TTL.. The quick re-use and TTL feature can only be used in a dedicated Azure Integration runtime.

You may want to switch to a Dedicated Azure IR-
Create a dedicated Azure Integration Runtime instead of using AutoResolve here TTL can be configured  (e.g., 10–30 minutes) to keep the cluster warm between executions.

You can even refer this article for more understanding-
Auto Resolve Azure Integration Runtime Vs. Dedicated Azure Integration Runtime

https://learn.microsoft.com/en-us/azure/data-factory/concepts-integration-runtime

Hope this clears some air!

 

View solution in original post

1 REPLY 1
v-sdhruv
Community Support
Community Support

Hi @mlord ,

AutoResolveIntegrationRuntime does not allow TTL configuration directly in JSON or UI. This IR is managed by Microsoft and dynamically resolves to the best region, but lacks customization options like TTL.. The quick re-use and TTL feature can only be used in a dedicated Azure Integration runtime.

You may want to switch to a Dedicated Azure IR-
Create a dedicated Azure Integration Runtime instead of using AutoResolve here TTL can be configured  (e.g., 10–30 minutes) to keep the cluster warm between executions.

You can even refer this article for more understanding-
Auto Resolve Azure Integration Runtime Vs. Dedicated Azure Integration Runtime

https://learn.microsoft.com/en-us/azure/data-factory/concepts-integration-runtime

Hope this clears some air!

 

Helpful resources

Announcements
Fabric July 2025 Monthly Update Carousel

Fabric Monthly Update - July 2025

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

August 2025 community update carousel

Fabric Community Update - August 2025

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

Top Solution Authors
Top Kudoed Authors