Added FAQ for Maximum Repair Tasks

Author: Saket Harsh

articles/service-fabric/service-fabric-patch-orchestration-application.md

@@ -433,6 +433,10 @@ It might also be possible that node patching is blocked because it's stuck in *D
 
 A: POA disables the node with a *Restart* intent, which stops or reallocates all the Service Fabric services that are running on the node. POA does this to ensure that applications don't end up using a mix of new and old DLLs, so we recommend not patching a node without disabling it.
 
+**Q: What is the maximum number of nodes that can be updated using Patch Orchestration Application?**
+
+A: Patch Orchestration Application uses Service Fabric Repair Manager to create repair Tasks for nodes for Updates. However no more than 250 Repair Tasks can be present at the same time . Currently Patch Orchestration Agent creates repair Tasks for each node at the same time. So , POA can update no more than 250 nodes in a Cluster. 
+
 ## Disclaimers
 
 - POA accepts the End-User License Agreement for Windows Update on behalf of the user. Optionally, the setting can be turned off in the configuration of the application.
@@ -512,4 +516,4 @@ An administrator must intervene and determine why the application or cluster bec
 - Changing default value of InstallWindowsOSOnlyUpdates to False.
 
 ### Version 1.3.2
-- Fixing an issue that affects the patching lifecycle on a node, if there are nodes with a name that's a subset of the current node name. For such nodes, it's possible that patching was missed or a reboot is pending.
+- Fixing an issue that affects the patching lifecycle on a node, if there are nodes with a name that's a subset of the current node name. For such nodes, it's possible that patching was missed or a reboot is pending.