Add troubleshooting documentation for post-upgrade flow failure notifications #10753
+302
−4
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.
Users report receiving "Sync Issues to Azure DevOps" emails after Core Components upgrades despite not using Azure DevOps, ALM Accelerator, or Innovation Backlog. Investigation reveals no flow with this name exists—these are Power Platform's automatic failure notifications when the "Admin | Sync Template v3 Configure Emails" flow attempts to configure partially installed or unconfigured optional CoE components.
Changes
New troubleshooting document (
docs/TROUBLESHOOTING-AZURE-DEVOPS-EMAILS.md)Updated main troubleshooting guide (
TROUBLESHOOTING-UPGRADES.md)Issue response template (
docs/issue-response-templates.md)Improved discoverability (
README.md,Documentation/README.md)Key Insight
This is expected behavior, not a bug. Power Platform sends automatic notifications when flows fail. Users receiving these emails have optional CoE components (Innovation Backlog, ALM Accelerator, Pipeline Accelerator) that are installed but not fully configured. Resolution: turn off unused flows or remove unused solutions.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.