Hello All,
I am hoping someone will be able to assist me with a workflow that just wont complete.
I have an Alteryx workflow I inherited from an individual that left my team. This workflow was simple enough (even if messy), merges three files and enriches with some attributes from a few dimensions. This workflow used to run in under 3 minutes. I ran the workflow on my local pc several dozen times over a few weeks without issue until one day it started running without issue or error but never completes (left running over night and still not completed). There is no error and the dataset size has only grown slightly.
I gave this workflow to another team member and it runs on their local in under three minutes (no changes made). Completing the workflow as expected with no issues.
I rebuilt the workflow from scratch and it went back to being under three minutes for a week or so before encountering the same issue.
The issue has now occurred with a second workflow that is far larger (Essentially functioning as an ETL tool). Used to run in about 50 minutes but now never completes. Other users can run the same workflow in around 50 minutes as expected. This workflow will take far longer to rebuild from scratch (of course its also inherited but from a different individual who left my team).
Is this an Alteryx or workflow environment setting that is causing this? Has anyone encountered something similar and resolved the issue?
What is confusing me is that its only affecting my local Alteryx and others can execute the workflows as expected.
I have tried disabling AMP and ticked "Disabled the Auto Configure" (under User settings). My Alteryx version is 2024.2.1.14 (same as the rest of my team)
Regards
If the same flow is working on different machines but not on yours, then the first thing that I would check will be the available memory on your computer.
Hi @Kelmdk
Does the workflow get 'stuck' at the same point when it's running on your machine? This could be at a Join potentially, that would be a good start to identifying what is going on.
I agree with others that this is likely a memory issue. Two types, though, so let me explain what I’ve experienced before:
But since you mentioned this workflow runs for a number of times, and then gets hung up a few weeks in, this sounds more like a cache'ing or local memory (hard drive space) issue.
I would also recommend, if you haven’t already, remove any/all BROWSE tools since they cache additional instances of the data at any/all of those points. This could also help avoid redundant or unnecessary storage use.
If all that fails, open a service ticket so that one of the support team can review your log files and maybe they can see what’s going on or where it’s hanging up.
Hope that helps, -Jay
User | Count |
---|---|
107 | |
82 | |
70 | |
54 | |
40 |