Skip to content

Commit e3f2be4

Browse files
Merge branch 'dev' into psl-sql-uami-least-privilege
2 parents 4abbc6d + c6f19ab commit e3f2be4

File tree

1 file changed

+1
-15
lines changed

1 file changed

+1
-15
lines changed

docs/TroubleShootingSteps.md

Lines changed: 1 addition & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -533,20 +533,6 @@ If the server was deleted, either restore it (if possible) or update references
533533
</details>
534534
535535
536-
<details><summary><b>DeploymentCanceled(user.canceled)</b></summary>
537-
538-
- Indicates the deployment was manually canceled by the user (Portal, CLI, or pipeline).
539-
540-
- Check deployment history and logs to confirm who/when it was canceled.
541-
542-
- If accidental, retry the deployment.
543-
544-
- For pipelines, ensure no automation or timeout is triggering cancellation.
545-
546-
- Use deployment locks or retry logic to prevent accidental cancellations.
547-
548-
</details>
549-
550536
<details><summary><b>BadRequest - DatabaseAccount is in a failed provisioning state because the previous attempt to create it was not successful</b></summary>
551537
552538
- This error occurs when a user attempts to redeploy a resource that previously failed to provision.
@@ -590,4 +576,4 @@ Once your request is approved, redeploy your resource.
590576
</details>
591577
592578
💡 Note: If you encounter any other issues, you can refer to the [Common Deployment Errors](https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/common-deployment-errors) documentation.
593-
If the problem persists, you can also raise an bug in our [MACAE Github Issues](https://github.com/microsoft/Multi-Agent-Custom-Automation-Engine-Solution-Accelerator/issues) for further support.
579+
If the problem persists, you can also raise an bug in our [BYOC-Client Advisor Github Issues](https://github.com/microsoft/Build-your-own-copilot-Solution-Accelerator/issues) for further support.

0 commit comments

Comments
 (0)