I agree with fabio - there is definitely something fishy going on when you set a value in a Boolean column in a set columns action. And it doesn’t matter whether you write “1”, “true”, “TRUE”, “True” or any other reasonable value. The problem is that the value is stored as text.
But it is very hard to figure out, as it seems like Glide to some extent cope correctly with the text value. It is even presented correctly in a Boolean column (see picture below):
However, Sheets is not fooled. If you try to treat the corresponding cells in Sheets as Boolean values it will not work, because Sheets recognize it as text - it turns out that the cell actually contains 'TRUE and not TRUE, i.e. Sheets see it as text.
Consequently, you can’t expect that you can use any kind of logic in Sheets correctly on these values - unless you know what is going on.
Why Glide works like that I have no clue. But it is extremely tricky to figure out why your app doesn’t work when you try to set a Boolean value in a set columns action. My workaround has been to change the Boolean column to a text column and then fill it “Yes” and “No” values instead. Then I’m not in doubt, that it is actually a text value. But, of course, if you need to set values in the same column in a checkbox component too that workaround will not work.