Why do I get denied access to Flow Designer execution?

[thomaskennedy]

When I open More Options | Executions and try to view the execution history I get an exception.

It says There was an error loading the execution details for this flow context.
Exception while executing request: User doesn't have permission to view the report.

If I look in the system log there is an error which says the probem is occurring in some REST api.

I'm an admin in this environment, and I've assigned myself every role under flow designer etc.

The records on the Executions tab are in the sys_flow_context table. If I open that table the records open just fine. But on the form there is a ui action named Open In Operations view.

All that action does is:

function openOpsView() {
  var id = g_form.getUniqueValue();
  window.open('/$flow-designer.do#/operations/context/'+id,"_new");
}

This button produces the same exception the Executions tab does. I suspect the problem is in the operations view.

So what is this operations view and where can I find it? I suspect it is trying some magic that is blowing up.

[mkm1]

Is your system property com.snc.process_flow.reporting.level is set properly?  If not please, try setting it. 

[Hemanth M1]

Hi @thomaskennedy ,

It could happen for couple of reasons 

1)Is this happening in your sub prod instances??? if yes , did you clone recently?? if yes , Please remove all your roles and re add it again - (i have experienced this personally) 

2)As mkm1 saying :  "com.snc.process_flow.reporting.level" property is off, if this is the case it would display in the exception error to set this property, i wouldn't recommend this turn on in prod (since its a global setting setting and impact performance ) if its only for debugging , turn on/off per flow basis.

Thank you,

Hemanth

[thomaskennedy]

Hemanth,

This is happening in subprod. I believe we have only one Flow in prod, and its reporting is turned off anyway, so there is nothing to check there.

We have not cloned recently - but I will try the roles as you described.

Our admin is seeing the same behavior:

When he checks the executions for a flow whose reporting is set to OFF, he sees the informational  message that says reporting is off; when he checks the executions for a flow that is capturing reporting data, he sees the same exception I'm getting.

The net result is that we can write Flows but cannot troubleshoot them. I expect we will open an incident about this.

[Hemanth M1]

Hi @thomaskennedy ,

1)I would try setting the property "com.snc.process_flow.reporting.level" to "Trace" once (by clearing cache), executing the new flow to have a new context.

2)Redding roles