How to resolve: The column no longer exists

Hi everyone! Wanted to provide some documentation for one of the most common error messages we are contacted about.

When you receive a payload from an API, the payload can include different columns based on the data being transmitted. This means that the columns that you used to build your Flow’s logic may not always be present in future requests, which can cause the entire Flow to fail.

This causes the error message: The column {api.Column} no longer exists.

To resolve this error message, we can use the Insert Text Column step to create a placeholder column with the same name as the column referenced in the error message. At the top of the step, check the box that reads, “Skip if column exists.” This ensures that the column will only be created if it is not present in the data. For the column value, you can simply set the value to be one space.

You may have to add multiple columns based on your Flow, but this solution should keep the Flows from failing!

Feel free to comment below with any questions or issues – hope this helps!

Thanks Adam! This seemed to be the issue. Kev

1 Like

BEFORE or AFTER the missing column step ??!?! This needs to be checked as its unclear !

Hi @Amy,

You place the Insert Text Column before the step with an error. Generally speaking, you can place the step directly after you’ve expanded all of your JSON. Let me know if you have any additional questions!