Diagram Flow not displaying anything

[JLeong]

Hi Guys,

First, the Diagram Flow was grayed out because of the following error:

So I removed the Error Handler, and then it let me toggle between the 2 views, however the Diagram is empty:

Am I missing anything?

Thank you!

[Maurice Murphy]

After speaking with Now Support, they let me know that this is related to a known problem in Vancouver (PRB1723237).

I will say that I faced this issue before we upgraded to Vancouver (if memory serves I've had it since Tokyo, at minimum), but they've provided a workaround via KB1585758, and stated it will be fixed in the Washington, D.C. release. I ran their provided script and am now able to get the diagram toggle to work again.

Here's the script from the KB (linked above):

// IMPORTANT: Run script in scope: sn_diagram_builder
var gr = new GlideRecord('sn_diagram_builder_node_type_handler');
gr.get('369c7d0b77b470104f27ceec8e5a9912');
gr.query();
while (gr.next()) {
    gr.deleteRecord();
}

[marcos_castro]

That solved the problem! I checked that my Washington PDI doesn't have the record as expected, so it's probably solved on that version already as they said

[JLeong · Accepted solution]

Yes, this issue is fixed in Washington!!!

[Adam43]

interesting, my Vancouver Patch 8 instance- it does not work and Washington patch1 hotfix2 it does work.

when i compare the record that script deletes on the sn_diagram_builder_node_type_handler table- the xml's are exactly, 100% the same. so it must be included in VancouverPatch8.  but yet still doesn't work for me......

I say that- because when I try running the script in scripts background- I get the following error and it won't delete that record

Security restricted: Delete operation against 'sn_diagram_builder_node_type_handler' from scope 'rhino.global' has been refused due to the table's cross-scope access policy

[marcos_castro]

This error is probably happening because you're trying to run a script that's on a scoped application. I had the same problem and the easier route I found was to export the record XML, edit the active field to false, and upload it again to my instance, so instead of deleting I deactivated it which has the same effect