Flow Designer - Unable to Edit Flows in Production Instance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
Hi Community,
I'm encountering an issue with Flow Designer in my production instance — I'm unable to edit any existing flows.
I've already tried assigning the following roles to my user account, but none of them have resolved the issue:
• admin
• security_admin
• flow_designer (if applicable)
Could someone please clarify:
1. Are editing flows intentionally restricted in production instances by design?
2. If not, what specific role(s) or configuration changes are required to gain edit access in a production environment?
Any guidance or documentation references would be greatly appreciated. Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday - last edited Monday
Hi @lavetisaiku
Refer: KB2659834 Admin users unable to edit flows in flow designer
Resolution
- To restore editing capability, assign the flow_write_enabled role to any users who are authorized to create, modify, or delete flows in Flow Designer.
- Once this role is added, users will regain full write access, and the issue will be resolved.
Refer: KB2657286 Unable to Edit or Create Flows/Subflows in Flow Designer After Platform Upgrade
Resolution
1. Locate the sys_dictionary record for the sys_scope column on the sys_metadata table.
2. Ensure the "default value" is set to the scope of the current application. If it is empty, revert the record to the latest version.
3. After updating the default value, verify that flows and subflows can be edited and created as expected.
If nothings works , Repair the Workflow Studio plugin.
If still not working, Raise a case (Hi Ticket) with ServiceNow Vendor
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti