
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Sep 13, 2023 03:24 PM
Today any script that I was using remoteFetchAsync (to avoid CORS errors) is giving me this error:
j: Error: Bad request: <root>.requestJson is missing
This error comes up on a few requests to different unrelated APIs. Additionally, some which work using regular fetch give this error when using remoteFetchAsync.
These scripts were working fine until now. Any ideas?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Sep 14, 2023 12:54 AM
Happening for us too. Business critical - customers are delayed 😬
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Sep 14, 2023 01:27 AM
We have same problem and this fixed it for us. thank you so much for posting you saved us a lot of pain
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Sep 14, 2023 01:51 AM - edited ‎Sep 14, 2023 03:31 AM
Hello,
I am also experiencing the same problem and is preventing me from delivering a project. The browser extension does not work on my side and using "fetch" results in a CORS error.
Any guidance on how to overcome the issue will be fantastic.
Many thanks,
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Sep 14, 2023 02:10 AM
+1
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Sep 14, 2023 02:15 AM
just use fetch api instead of remoteFetchAsync it worked for me
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Sep 14, 2023 02:53 AM
Does anyone have a solution for this or an answer if it's an Airtable's side issue that will be fixed or not (both fetch and remoteFetchAsync are not working)?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Sep 14, 2023 03:11 AM
Not sure the mentioned CORS browser extension does not work on Airtable "fetch" script on my side (MS Edge) as it got blocked by Airtable client side script regardless of CORS is bypass or not.
Especially, when my targeted remoteUrl is another airtable webhook. Sadly no server side modification could be done here.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Sep 14, 2023 04:34 AM
same problem here. using fetch is not possible for us because we can't change cors settings. hope this gets solved very soon.

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Sep 14, 2023 04:38 AM
Same problem here!
Don't really want break everything by trying workarounds...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Sep 14, 2023 04:46 AM
yea same here tried almost everything and i think its on the side of airtable as they were rolling out new stuff for automations as some of the mails they have been sending suggested me.
And for me the fetch is working I dont know how i didnt do any workaround or something. I just replaced the removeFetchAsync with fetch and it worked fine
