Within an Automation Script, it's frustrating that we still encounter the inability to update the Single Select or Multi Select field options, with the error returning;
"Airtable "Error: Cannot update field config from scripting automation"
This limitation forces the user to reconsider the field type, with the alternative solution usually swapping it into a Single Line text field.
Interestingly, it is possible to use an Automation Update Record action to do this exact same process, but for whatever reason it's not possible for an Automation Script to execute this very same process.
Can this limitation please be reviewed and reconsidered by Airtable Developers? Without this feature, it limits the use of Single Select and Multiple Select fields within bases heavily dependent on Automations.