If course all devs would like to get helpful error messages. But we don’t always get them. So we must try to work with what info we do get.
Airtable tries to provide helpful error messages when it can. Sometimes it can’t. Plus, sometimes a vague error message is better than an incorrect error message that can lead one down incorrect rabbit trails. (For example, whenever a fetch doesn’t work, Airtable suggests cors errors, even when cors is not the issue.)
The best way to get better error messages in the future is to contact Airtable support with your issue and hope Airtable’s engineers can reproduce your issue and debug it. As this is a community forum, there is no guarantee that an Airtable employee will see your post here.