From time to time, Data360 Analyze users may see the following error message while attempting to open or save changes made to their data flow:
STEPS TO RESOLVE:
In this case, we recommend that you perform the following steps:
1. Export the data flow to somewhere safe
2. Delete the data flow from Data360 Analyze
3. Import the data flow back into Analyze. If possible, save it under a different name or in a different folder than the original.
If this doesn't work, please raise a support ticket and our team will be happy to help you troubleshoot the issue
Comments
4 comments
Hi Christina,
This message only happened to my access ID and the other user not having any issue when try to open the flow impacted.
Hi Yusairi, what version of Analyze are you running?
Hi Christina,
I'm using Data3Sixty Analyze v3.4.3.5100.
Same as what my team mate access to.
Since the origin flow had been back-up, I took a risky way to export the existing flow that I can't open (I don't want to waste my time to re-draw all the new changes had been made). Then, import back under the same folder and overwrite the existing flow.
Then, I am be able to access. In addition, I had requested my team mate to access from their side and they can access as usual with the latest new changes I had made.
I don't if this is a correct way but based from your step, I am follow step 1 and step 3 in same folder and overwrite the existing flow.
Maybe you can advice more why it's happen.
Hi Yusairi,
It fails because the application cannot find the edit session (user token) object where your updates are stored before they are saved. The reason it doesn't happen for other users is because the edit session that they use exists. Each user has its own edit session for each data flow that is edited, even if the data flow is shared.
Would it be possible for you & your team to upgrade? This issue is fixed in later versions.
Please sign in to leave a comment.