Hey @kurtwz
Can you enable performance profiling in designer and this will tell you where it's taking longest?
My gut says it will be the write back to SQL
Hey @LordNeilLord, thanks for the reply. I've turned on Performance Profiling. I also deleted the browse tools on the inputs. I can't run it again right away because my edit permissions to the DB are messed up at the moment (unrelated to the performance issues, most likely). Trying to get that fixed. Will run again soon and let you know how it goes. - Kurt
OK here's the update: I got the DB issues resolved that were unrelated to the issues I'm experiencing with this workflow. I also turned on the performance profiling. Unfortunately, the performance profile hasn't helped much this morning because I now get errors with Workflow 2. I still get information on how long certain steps of the workflow took, but the workflow won't run to completion successfully with the errors I'm getting. Here is how the performance now stacks up:
Workflow 1: Still running at around 3 minutes. Most of the time is spent writing to the DB and has been tweaked as much as possible. 3 minutes is an acceptable time to run. I'm turning my attention to Workflow 2.
Workflow 2: This consistently experiences errors and does not run to completion. I tried three times this morning. Got two errors related to two of the SharePoint inputs timing out (same ones each time). These two SharePoint inputs have the two highest number of records in them at 7500 and 12600. I realized that the list with 7500 records is no longer needed. Consequently it has been disabled. However, the one with 12600 records is still needed, so I have to figure out how to make that run.
The Excel file that this workflow will replace is able to refresh all the data for all the feeds in 2-3 minutes. In Excel I broke out the feed that we're having problems with in Alteryx and ran that one individually and it ran in about 1 minute. Can anyone please tell me what I need to do in Alteryx to get the input tools from SharePoint to retrieve data any quicker?
Thanks, Kurt
Hey all, still need some input on this, if anyone has advice or information to share. Thanks! Kurt
This is not a solution but Debugging steps
1. If possible recreate the whole workflow.
2. If not save the current workflow and delete tools each one from the end to see which one is the issue
3. i will also run 2 other tools like Fiddler or wireshark (for advanced issues ) to see if network delay in some calls
Everyone knows that debugging is twice as hard as writing a program in the first place. So if you are as clever as you can be when you write it, how will you ever debug it? ~Brian Kernighan