Document ActivityTimeout interaction with route-level Timeout in YARP #36287
      
        
          +44
        
        
          −3
        
        
          
        
      
    
  
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
ActivityTimeout(default 100s) silently limits route-levelTimeoutvalues, causing confusion when configuring timeouts longer than 100 seconds.Changes
Timeoutgoverns total durationTimeoutdisabled when debugger attached,ActivityTimeoutalways appliesActivityTimeoutper clusterActivityTimeoutapplies to WebSocket requests and that WebSocket keep-alives can prevent idle timeoutsExample
{ "Routes": { "longRunning": { "ClusterId": "cluster1", "Timeout": "00:05:00" // 300s - will be limited by ActivityTimeout's 100s default } }, "Clusters": { "cluster1": { "HttpRequest": { "ActivityTimeout": "00:10:00" // Increase to 600s to honor route timeout } } } }ActivityTimeoutyarp#2950Original prompt
ActivityTimeoutyarp#2950💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.
Internal previews