Flow designer error

[Santiago Musca]

Hello All,

I'm testing an OOO DevOps flow in Flow Designer. It is the "DevOps Integration - Discover", it is autoamtically added once you install the DevOps Change Velocity app in your instance. The error I'm receiving is one that I couldn't find in the documentation, nor the community. 

The error says: "Attempted to add black listed role: [*Here it is a sys_id that doesn't exist in the instance*]".
Having a look at the flow engine context, I found this in one of the actions:

"com.snc.process_flow.exception.ProcessAutomationException: Attempted to add black listed role: [*sys_id*]" 

I don't really know what it means and how to solve it, so any suggestion is welcome.

Thanks!

[Luxo Nadappan]

hi, 

Have you  checked all the roles related to dev ops are installed otherwise please repair the installation. 

Also you can try going via "https://docs.servicenow.com/bundle/vancouver-devops/page/product/enterprise-dev-ops/concept/dev-ops-...

It was pretty straight ford installation and i was able to connect azure dev ops and related insights recently.

Regards,

Luxo

[ylarhantec]

Hi All

Same error here when trying to discover repository from a Bitbucket tool.

I have the 6 expected roles.

Regards,

Yann

[Sunil Mitkari]

Go to flow properties and check if it has role in run with roles. if present copy the role, Open that role form sys_user_role table, check if it contains any of the roles which are deleted or not present. Try not to have the roles deleted.

[Santiago Musca · Accepted solution]

Hello all.

Sorry for the delay. The project was on hold for some time and after that I forgot to add the answer here. After a ticket with ServiceNow, we found that the problem was as follows: 

The main issue was that under the 'Contain Roles' related table, inside the ‘sn_devops.viewer’ and the ‘sn_devops.tool_owner’ roles records, there was a role named '(empty)' (the SN employee also told as that it could also be named 'sn_change_read is listed'). After we removed it, and checked that the sys id was not in the XML file, the issue was solved.