This workflow seems to crash Alteryx across different installs (server and desktop tested)
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
No reason this should fail. Hits 1+ GB of data, but tiny compared to some problems I've worked with. Crashes anytime I look at the data at any tool. https://www.dropbox.com/s/tybox2qjcn5qhjb/DataIntegrationMetaKagge%20v2.yxzp?dl=0
Solved! Go to Solution.
- Labels:
- Error Message
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Is there a particular error that you are getting? My laptop runs this workflow in just under 30 seconds.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Also no issues looking at the data in any of the tools. I am currently running Alteryx 2019.3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Interesting, I was just able to replicate Alteryx closing by clicking on the right anchor of the sort tool. Upon further investigation it looks like the PrivateScoreFullPrecision field is what is causing the issues. When I try to convert it to a fixed decimal I get this: inf is not a valid number
@DiganP this is the workflow that we are taking a look at
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Found a way to fix it!!! Set the PrivateScoreFullPrecision to a double instead of a float in the beginning of the workflow.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Nice. Thanks @BrandonB. Nice fix even if it leaves the underlying issue in place. Don't imagine I'm likely to have the same problem again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
I will also forward this to folks who can take a closer look at what is going on. Thank you for reporting this!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
I can now, sadly, report that changing the requested field to double does nothing. Still crashes when I look at the outcoming data from Tool 25.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
The issue is definitely with the PrivateScoreFullPrecision. Tool 25 as you have it configured creates a new field from PrivateScoreFullPrecision and set it as a float. If you change this data type output to a double as well it fixes the issue.
![](/skins/images/5A278AAD67B5F68761E04A0A1AFFBB3D/responsive_peak/images/icon_anonymous_message.png)