Ugg, I’m not an expert on how these things work with Airtable. Normally I would have a separate table that lists all of the status options in separate rows. That separate table would be the source table for the choice component, and then your choice component would write the value to your form destination table. That logic makes sense to me.
But it seems that Airtable lets you have different column types that serve dual purposes. In this case, it contains the list of options as well as holds the value of the selected choice. If I’m understanding correctly, you are trying to use the same column as both your source and your destination, and that doesn’t play well with glide.
This is similar to Linked Records that hold the value for a relation as well as serve as the relation. Glide has some workarounds in place to handle these types of Airtable columns but I’d say it’s not standard procedure to set things up like this.
I think in your case, you can get away with it as long as you create a separate table with all of your choices, and then use that as your choice component source.