Can not view the flow execution details in washington. getting redirected to the default form view.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-18-2024 05:25 AM
I am not able to see the execution details of any action/flow/subflow. I have configured the reporting level to ON.
it is just opening the execution context record in the default form view.
even upon clicking the open the operations view action it again gets redirected to this view. I am saying redirected because upon clicking the action initially browser looks for https://dev191239.service-now.com/$flow-designer.do#/operations/context/ba61f07c64d242109e1d1e99d019... this link but later gets redirected to the above view. Please help!
- Labels:
-
Flow Designer
- 4,655 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2024 07:27 AM
hello @kundusuman328 i faced the same problem and it's fixed by updating the workflow studio to the latest version ( install of "Unified Developer Core " is required also).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2024 10:27 AM
Hi,
I also have a fresh Washington DC PDI and I have this view as well. Same as @kundusuman328
How do I change it so I can see the flow?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2024 04:59 PM
Having the same issue, as @kundusuman328 . I can't view Flow Execution Details even after updating to the latest version of Workflow Studio. 'Operations View' redirects back to the same page (flow engine context). I turned on reporting.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2024 11:19 AM
Have you find any solution for this issue? I am facing same issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-20-2024 05:28 AM
Hi,
I got it to work for me know.
I've repaired the plugin but that didn't help. Then I updated it to version 25.2.5 and now I got the correct debug