Regarding this old issue:
The underlying cause has been fixed, as per Airtable support. I stumbled upon it in a completely different scenario and reported it around a month ago. You can verify by clicking and holding either arrow button of an input.config.number element inside the Scripting app settings UI. Doing so would have thrown an error before (after around 15 reactions, I suspect ) and it doesn’t any longer.