Flow is not redirecting to current flow from Preview Record button

Nisha15
Mega Sage
Mega Sage

Hello Experts,

I have noticed one behaviour in next experience. So when we try to open flow record from preview button, instead of opening that flow record it is redirecting to workflow studio homepage. refer the below attached screenshots:

1. This is the ootb catalog item where flow has been used:

Nisha15_0-1714043437401.png

2. Once clicking on open record the page which it is redirecting me to, with the error:

error message:  Asset not found: Check the Sys ID, Builder ID, and Table name for any errors before trying again.

Nisha15_1-1714043502137.png

 Note: One thing I noticed is once we click on open record it is redirect to this link first followed by your instance name:/$flow-designer.do?sysparm_nostack=true#/flow-designer/8c599a89eb2191100290e744d852283f?sys_id=8c599a89eb2191100290e744d852283f&sysparm_view=
but automatically referesh to this link: /workflow-studio/home/process(which is causing to open workflow studio homepage)
This is behaviour is there in both PDI and customer instance.
Has anyone noticed this behavior? I think this is the next experience issue, but can someone else also confirm.

Thanks in advance,

Nisha

 

1 ACCEPTED SOLUTION

Nisha15
Mega Sage
Mega Sage

I have made a workaround for this issue. You can access the solution here: https://www.linkedin.com/feed/update/urn:li:activity:7199764259986186241/

View solution in original post

5 REPLIES 5

NOTNEEDED
Tera Contributor

We're seeing the same behavior in our instances as well, after the Washington DC upgrade.  I submitted a support ticket today on the issue.  Will try to add an update here when the ticket is resolved.

NOTNEEDED
Tera Contributor

Received a response from Support.  This is a known issue, documented in PRB1744959.  Guidance provided is:

1) Upgrade the impacted instance to Washington DC Patch 3
2) Update Workflow Studio to version 25.2 to address the issue

Nisha15
Mega Sage
Mega Sage

I have made a workaround for this issue. You can access the solution here: https://www.linkedin.com/feed/update/urn:li:activity:7199764259986186241/

NOTNEEDED
Tera Contributor

Nice workaround.  Thankfully, we were able to fix this issue by upgrading to Washington DC patch 3, as suggested by Support (washingtondc-12-20-2023__patch1-hotfix2a).  I recommend the same for anyone else facing this issue.