Compute nodes that compute a new output field have been incorrectly storing an "input" reference to this output field, and this problem is now seen when you edit and save an analysis that has Compute nodes that do this. Existing compute nodes that are computing a new field would show this problem when edited and need one more accept & save to clean them up, wherever they are. Not to make them execute, but to clean up the incorrect reference information
What you need to do: If you are editing your analysis in UAT or Production directly, you need to select the Compute Node and click "Accept Changes" to correct the Compute node's reference and save the analysis
If you encounter any technical issues, we recommend that you visit the support portal at support.precisely.com