Fields show as missing despite data present in upstream tool

[MemphLantAntonio]

This seems to have started when I thought my company upgraded from 2021 to 2022. It also asked to upgrade workflow to AMP. There are a few strange messages from my workflow at the top of my image including "the following tool ids are using an e1 compatibility layer with 24 conversion points" and "beginning to compact waiting packets to reduce memory usage". I had previously never seen these.

Esentially I will have a tool (pictured) where the input has data but the output after a Table tool has no data. Issue seems to be with Table, Report Text, and Email tool. In image, you will see that the join I am using (I have used this configuration successfully int he past) doesn't recognize that there are any fields in the upstream tool and thus doesn't let me join. Reading other posts, I tried creatign Dummy text tools and finishing out the workflow, but still doesn't work on the server. Also checked the Disable Auto Configure is unchecked. 

I am having similar issues with all of my workflows, and it is making Alteryx almost unusable. Please help!

Thanks!

[caltang]

This could be a cache issue. Try deleting the Join Multiple Tool and replace it with a new tool. Then use the same configurations and run. If it works, great. If it doesn't, then it means your previous tools have some configuration issues. Try clicking on the Report tools prior to the Join and ensure that they are working accordingly with no missing fields.

Sometimes, what I've observed when upgrading versions, is that when a tool stops functioning, clicking on it or replacing it usually works. Try and revert - see if we can do more.

Also if you can.... export your workflow with dummy data so we can see the configuration of each tool. You can mask the sensitive stuff with dummy/fake data and change URL / storage paths so we cannot identify you for your safety.

[danilang]

Hi @MemphLantAntonio 

"IT asked to upgrade workflow to AMP" is not a good enough reason to actually perform the upgrade.  There are enough differences between original and AMP that workflow conversions are a significant effort when you consider development and testing time.   If your workflow was running fine using the original engine then continue using the original engine.  I would recommend using original for all legacy workflows unless there is a specific performance reason to change.  Any new workflows that you develop can target the AMP engine.

Dan    

[MemphLantAntonio]

This had been driving me crazy. These are my observations: it seems like it was related to a dynamic input where the workflow had not been run but also that as I was reorganizing my workflow I had tools without inputs. For some reason, if I cache the dynamic input, any tools with nothing feeding it yet ("missing incoming connection"), and then F5 refresh, I see the fields again.