Clearer warning when a column is removed but still in a query

[dean-breed]

The warning is not clear enough for people to work out it is due to a column missing. Need to consider something more specific

[edwinmp]

@dean-breed ... I know this happens, but I can't replicate it in any of my datasets ... could you please share a screenshot of it. Also, would love suggestions on the clearer warning.

[k8hughes]

Moving to backlog until we get details from @dean-breed

[dean-breed]

@edwinmp I'll create an example

[dean-breed]

So I believe the issue would occur like this here irrelevant of whether it was missing a column due to the data source itself changing or just because of a select. I think just a simpler error message will help in more plain English. I think people are less likely to read it in it's current form.

Would it be possible to isolate the first step that doesn't work and the column that doesn't exist that is being used in the step that doesn't exist? @edwinmp

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.