Share
Report
2Summary
Renaming an action (card) in Power Automate can break expressions and references across the entire flow. This creates unnecessary risk during normal refactoring and discourages basic maintenance. Actions should have stable internal identifiers separate from their display titles, or the platform should automatically update dependent references during renames.
Problem Description
In Power Automate today, renaming an action can silently break downstream expressions and references that depend on the original action name.
This means:
- A purely cosmetic change (updating a title for clarity) can break an otherwise working flow
- Errors may not surface until runtime
- Debugging is time-consuming because the breakage is indirect and non-obvious
Users should not have to fear breaking their entire workflow just because they want to improve readability or naming consistency.
Why This Is a Serious Usability Issue
Renaming steps is a normal and expected part of:
- Refactoring flows as they evolve
- Improving maintainability and readability
- Onboarding new team members
- Applying naming conventions
In modern development tools, display names and internal identifiers are separate. Power Automate currently conflates the two, making renames a breaking change instead of a safe operation.
Proposed Enhancements
Option 1: Introduce Stable Internal Action IDs (Preferred)
Each action should have:
- A non-editable, stable internal ID
- A user-editable display title
All expressions and references should bind to the internal ID, not the display name. Renaming the card would then be a safe, non-breaking operation.
This aligns with established best practices in:
- Workflow engines
- Programming languages
- CI/CD pipelines
- Low-code platforms
Option 2: Automatic Reference Updates on Rename
If stable IDs are not feasible short-term:
- When an action is renamed, Power Automate should:
- Scan the flow
- Automatically update all dependent references
- Validate that references remain intact
At minimum, the system should warn the user:
“Renaming this action will update X references across the flow.”
Expected Benefits
- Prevents accidental breakage of working flows
- Makes refactoring safe and predictable
- Improves flow maintainability over time
- Reduces debugging sessions caused by invisible renaming side effects
- Encourages clearer naming conventions without penalty
Current Impact on Users
Today, users must choose between:
- Leaving poorly named steps in place to avoid risk, or
- Renaming them and potentially breaking the workflow
Neither option is acceptable for a production-grade automation platform.
Conclusion
Renaming an action should never be a breaking change. Introducing stable action IDs—or at least automated reference updates—would significantly improve Power Automate’s reliability, usability, and developer trust.
Thank you for considering this enhancement.
All responses (
Answers (
