If a dynamic flow flowlogic doesn't run at runtime, the operationsview errors out with "Cannot read property 'operationsOutput' of undefined" - Known Error

If a dynamic flow flowlogic doesn't run at runtime, the operationsview errors out with "Cannot read property 'operationsOutput' of undefined" Description UI currently has a defect where it will not load the operations view if the dynamic flow evaluates to "not run". This will be fixed in Quebec and backported to Orlando.

Steps to Reproduce

Create a basic subflow: 1.) Create a subflow. "test subflow" 2.) Add an action (no inputs nor outputs are necessary) 3,) Publish subflow

Create a flow: 1.) Create an empty flow 2.) Add a trigger (doesn't matter what trigger, go with a time based trigger for easiest setup) 3.) Add a Lookup Records action for table "Incident" 4.) Set the condition to "short description is asdfhaisg". Basically a nonsensical string that will return zero records 5.) Add a For Each flow logic 6.) In For Each, add pill "Incident Records" from step 3 7.) Add "Dynamic Flow" flowlogic underneath For Each, add "test subflow" as the Flow Template and "test subflow" as the second input "Flow". 8.) Save and Test this flow. Click the ops view link once test has finished. 9.) Observe "Cannot read property 'operationsOutput' of undefined" error

Workaround This problem is currently under review and has no workaround. To receive notifications when more information will become available, subscribe to this Known Error article by clicking the Subscribe button at the top right of this form. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.