We see canvasses every day where dozens fields are brought into a canvas or a macro, but never used - and this just creates slowness for no good benefit.
Given that one of the selling features of Alteryx is the speed of processing - could we look at three improvements to the Alteryx engine & designer:
easiest: Keep track of every field brought in / created - and if they are not used in an output, then throw a warning at the end of the execution process
For example - you bring in fields a,b,c - you create field d and e during the flow in formula tools
Field d is never used as an input to any filters or formulae - and it doesn't appear on any output - so it's just waste
Field a and b are part of the output, so they are fine
Field c is never used at all - so that's just waste.
Field e is used to filter the records before output - so this one is fine.
So we've immediately found 2 fields that we can eliminate and make this canvas faster
Medium: Ignore the unused fields in the execution engine
Hardest: Tell the users that their field is unused in Alteryx Designer by doing a lineage analysis of the tools, just like software environments like Visual Studio do. This may require a change to the engine & to designer 'cause we would need to make each tool capture the full detail of the fields that they know in their configuration in order to do this trace.