Application is throwing error after deploying in new cluster

Question

Application is throwing error after deploying in new cluster

Pushkar Srivastava 0 Microsoft Employee

Application deployment is successful, but it is throwing the error in newly deployed cluster
Partition is below target replica or instance count.
error details

fabric:/AzureStackEdge/AgentWebRole -1 1

(Showing 0 out of 0 instances. Total available instances: 0)

For more information see: http://aka.ms/sfhealth

Anonymous

2026-04-13T09:22:19.46+00:00

It looks like this case is duplicate case for the subscription created over here: https://learn.microsoft.com/en-us/answers/questions/5847722/application-deployment-is-failing-in-newly-deploye

Hence marking this case as duplicate of the original one.

1 answer

Your answer

Anonymous

2026-04-13T09:22:19.46+00:00

It looks like this case is duplicate case for the subscription created over here: https://learn.microsoft.com/en-us/answers/questions/5847722/application-deployment-is-failing-in-newly-deploye

Hence marking this case as duplicate of the original one.

Answer 1

Hello Pushkar,

The message “Partition is below target replica or instance count” is a standard Service Fabric system health report generated by System.FM. It means the partition is currently running fewer replicas (stateful) or instances (stateless) than the service configuration expects. Depending on whether the partition is below the target count versus below the minimum allowed count, Service Fabric can report this as a warning or an error. (see: https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-understand-and-troubleshoot-with-system-health-reports#partition-system-health-report)

In your specific output, Total available instances: 0” indicates Service Fabric currently sees zero eligible nodes for placement. This generally happens when there are no nodes that are Up/healthy/available for placement, or when placement constraints/policies effectively exclude all nodes.

Can you please check below details and share us the details in Private Message:

Use Service Fabric Explorer to review cluster and service health, and confirm whether nodes are present and healthy (https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-view-entities-aggregated-health) or if you have access to run powershell commands then run Get-ServiceFabricNode and Get-ServiceFabricPartitionHealth
If nodes are up but instances still cannot be placed, run below commands and share us the details
```
   Get-ServiceFabricNodeLoadInformation 
   Get-ServiceFabricPartitionLoadInformation 
```
What does Get-ServiceFabricNode show for node status and health state (or what do you see in Service Fabric Explorer for node health)?
Is AgentWebRole a stateless service with InstanceCount = -1 by design, and does it have any PlacementConstraints or placement policies configured?
What are the specific health events returned by Get-ServiceFabricPartitionHealth for the affected partition?