Skip to content

Conversation

Copy link

Copilot AI commented Dec 16, 2025

Setup wizards show generic "Failed to turn on this flow" errors, forcing admins to manually check 8-15 flows to identify failures. Flow names are available in the data context but unused.

Analysis Deliverables

Comprehensive feasibility analysis across 7 documents (~60 KB):

  • Technical Analysis - Current implementation uses IfError() with generic Notify(). Initial Setup Wizard already implements specific messages in some controls, validating the pattern.
  • Scope - 13 Canvas Apps require 1-line changes to OnCheck handlers
  • Implementation - String concatenation with null handling: Coalesce(ThisItem.theName, "Unknown Flow")
  • Impact - 60-80% reduction in troubleshooting time (2-5 min saved per error), affects thousands of CoE Kit admins globally
  • Risk - Low (UI text only, no breaking changes)

Code Change Pattern

// Current (generic)
IfError(
    Patch(Processes, LookUp(Processes, WorkflowIdUnique = ThisItem.theGUID), 
        {Status: 'Status (Processes)'.Activated}),
    Notify("Failed to turn on this flow...", NotificationType.Error)
);

// Proposed (specific)
IfError(
    Patch(Processes, LookUp(Processes, WorkflowIdUnique = ThisItem.theGUID), 
        {Status: 'Status (Processes)'.Activated}),
    Notify("Failed to turn on '" & Coalesce(ThisItem.theName, "Unknown Flow") & "'...", NotificationType.Error)
);

Affected Wizards (13)

High Priority: Environment Request (user-reported), Initial Setup, Compliance
Medium Priority: Audit Log, Other Core, Teams Environment Governance
Standard Priority: BVA, Cleanup, Inactivity Process, Maker Assessment, Pulse Feedback, Training in a Day, Video Hub

Recommendation

Proceed with implementation - High value (user pain point), low complexity (proven pattern), minimal risk (UI only), ~7 hours effort


Note: This PR contains analysis documentation only. Implementation will follow in subsequent PRs per the phased roadmap (IMPLEMENTATION_ROADMAP.md).

Original prompt

This section details on the original issue you should resolve

<issue_title>[CoE Starter Kit - QUESTION] How to identify the flow errors on setup wizards</issue_title>
<issue_description>### Does this question already exist in our backlog?

  • I have checked and confirm this is a new question.

What is your question?

On Environment Request setup wizard, an error was seen while turning on the flows:

image

As there are so many flows we have turned on, the message does not specify which flow has the error and we have to go back end and check each flow.

Could we please make the message specific to flows?

What solution are you experiencing the issue with?

Core

What solution version are you using?

April

What app or flow are you having the issue with?

Admin sync Template- V3

What method are you using to get inventory and telemetry?

Cloud flows</issue_description>

<agent_instructions>Analyze the enhancement request described in the ticket. Provide a comprehensive evaluation that includes:
Understanding & Summary
Summarize the enhancement request in clear, concise terms.
Identify the core problem the enhancement aims to solve.
Feasibility Assessment
Determine whether the requested enhancement is technically feasible.
If not feasible, explain the blockers or limitations.
Proposed Implementation Approach (only if feasible)
Outline the required code, architectural, or configuration changes.
Identify all affected files, components, or modules.
Describe potential risks, dependencies, or compatibility considerations.
Step‑by‑Step Implementation Plan
Provide a detailed, sequential explanation of what changes should be made.
Include reasoning behind each step to ensure clarity for reviewers and maintainers.
Deliver the analysis in a structured format using headings, bullet points, and code blocks when necessary.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@AmarSaiRam This issue is being closed as its scope is now included in a newly created consolidated enhancement request for centralized management of orphaned components (Apps, Flows, Connection References) in the CoE Starter Kit.

New Issue Reference: [CoE Starter Kit - Feature]: FEATURE TITLE Schema and Connector Stability Enhancements for CoE Star…

Thank you for your contributions</comment_new>

Custom agent used: CoE Custom Agent
Specialized agent for triaging and fixing issues in the CoE Starter Kit. Always consult the official CoE docs and the team’s SharePoint notes first, then mine prior GitHub issues and the CoE Common Responses playbook.


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Copilot AI and others added 5 commits December 16, 2025 13:36
Co-authored-by: harini-2-y <235104376+harini-2-y@users.noreply.github.com>
…cement

Co-authored-by: harini-2-y <235104376+harini-2-y@users.noreply.github.com>
Co-authored-by: harini-2-y <235104376+harini-2-y@users.noreply.github.com>
Co-authored-by: harini-2-y <235104376+harini-2-y@users.noreply.github.com>
Co-authored-by: harini-2-y <235104376+harini-2-y@users.noreply.github.com>
Copilot AI changed the title [WIP] Improve error messaging for flow identification in setup wizards Analysis: Add flow name to setup wizard error messages Dec 16, 2025
Copilot AI requested a review from harini-2-y December 16, 2025 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[CoE Starter Kit - QUESTION] How to identify the flow errors on setup wizards

2 participants