add new error

Author: NirajC-Microsoft

docs/TroubleShootingSteps.md

@@ -38,6 +38,7 @@ Use these as quick reference guides to unblock your deployments.
 | **InsufficientQuota** | Not enough quota available in subscription | - Check if you have sufficient quota available in your subscription before deployment<br>- To verify, refer to the [quota_check](../docs/quota_check.md) file for details |
 | **MaxNumberOfRegionalEnvironmentsInSubExceeded** | Maximum Container App Environments limit reached for region |<br>This error occurs when you attempt to create more **Azure Container App Environments** than the regional quota limit allows for your subscription. Each Azure region has a specific limit on the number of Container App Environments that can be created per subscription.<br><br>**Common Causes:**<br>- Deploying to regions with low quota limits (e.g., Sweden Central allows only 1 environment)<br>- Multiple deployments without cleaning up previous environments<br>- Exceeding the standard limit of 15 environments in most major regions<br><br>**Resolution:**<br>1. **Delete unused environments** in the target region, OR<br><br>2. **Deploy to a different region** with available capacity, OR<br><br>3. **Request quota increase** via [Azure Support](https://go.microsoft.com/fwlink/?linkid=2208872)<br><br>**Reference:**<br>- [Azure Container Apps quotas](https://learn.microsoft.com/en-us/azure/container-apps/quotas)<br>- [Azure subscription and service limits](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits) |
 | **SkuNotAvailable** | Requested SKU not available in selected location or zone | - You receive this error in the following scenarios:<br>  - When the resource SKU you've selected, such as VM size, isn't available for a location or zone<br>  - If you're deploying an Azure Spot VM or Spot scale set instance, and there isn't any capacity for Azure Spot in this location. For more information, see Spot error messages |
+| **Conflict - No available instances to satisfy this request** | Azure App Service has insufficient capacity in the region | This error occurs when Azure App Service doesn't have enough available compute instances in the selected region to provision or scale your app.<br><br>**Common Causes:**<br>- High demand in the selected region (e.g., East US, West Europe)<br>- Specific SKUs experiencing capacity constraints (Free, Shared, or certain Premium tiers)<br>- Multiple rapid deployments in the same region<br><br>**Resolution:**<br>1. **Wait and Retry** (15-30 minutes): `azd up`<br><br>2. **Deploy to a New Resource Group** (Recommended for urgent cases):<br>   ```<br>   azd down --force --purge<br>   azd up<br>   ```<br><br>3. **Try a Different Region:**<br>   - Update region in `main.bicep` or `azure.yaml` to a less congested region (e.g., `westus2`, `centralus`, `northeurope`)<br><br>4. **Use a Different SKU/Tier:**<br>   - If using Free/Shared tier, upgrade to Basic or Standard<br>   - Check SKU availability: `az appservice list-locations --sku <sku-name>`<br><br>**Reference:** [Azure App Service Plans](https://learn.microsoft.com/en-us/azure/app-service/overview-hosting-plans) |
 
 --------------------------------
 
@@ -115,6 +116,7 @@ Use these as quick reference guides to unblock your deployments.
 |-----------------|-------------|------------------|
 | **AccountProvisioningStateInvalid** | Resource used before provisioning completed | - The AccountProvisioningStateInvalid error occurs when you try to use resources while they are still in the Accepted provisioning state<br>- This means the deployment has not yet fully completed<br>- To avoid this error, wait until the provisioning state changes to Succeeded<br>- Only use the resources once the deployment is fully completed |
 | **BadRequest - DatabaseAccount is in a failed provisioning state because the previous attempt to create it was not successful** | Database account failed to provision previously | - This error occurs when a user attempts to redeploy a resource that previously failed to provision<br>- To resolve the issue, delete the failed deployment first, then start a new deployment<br>- For guidance on deleting a resource from a Resource Group, refer to the following link: [Delete an Azure Cosmos DB account](https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/manage-with-powershell#delete-account:~:text=%3A%24enableMultiMaster-,Delete%20an%20Azure%20Cosmos%20DB%20account,-This%20command%20deletes) |
+| **ServiceDeleting** | Cannot provision service because deletion is still in progress | - This error occurs when you attempt to create an Azure Search service with the same name as one that is currently being deleted<br>- Azure Search services have a **soft-delete period** during which the service name remains reserved<br><br>**Common causes:**<br>- Deleting a Search service and immediately trying to recreate it with the same name<br>- Rapid redeployments using the same service name in Bicep/ARM templates<br>- The deletion operation is asynchronous and takes several minutes to complete<br>**Resolution:**<br>1. **Wait for deletion to complete** (10-15 minutes) before redeploying<br>2. **Use a different service name** - append timestamp or unique identifier to the name<br>3. **Implement retry logic** with exponential backoff as suggested in the error message<br>4. **Check deletion status** before recreating:<br>`az search service show --name <service-name> --resource-group <rg-name>`<br>5. For Bicep deployments, ensure your naming strategy includes unique suffixes to avoid conflicts<br>- For more details, refer to [Azure Search service limits](https://learn.microsoft.com/en-us/azure/search/search-limits-quotas-capacity) |
 
 ---------------------------------