+7Today any script that I was using remoteFetchAsync (to avoid CORS errors) is giving me this error:
j: Error: Bad request: <root>.requestJson is missingThis 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?
Best answer by Jessy_Hu
Hi all,
We want to thank you for everyones patience on this while the team investigated the errors. We can confirm that the issue should now be resolved and the remoteFetchAsync() method can be utilized as normal. The fix also resolves related issues when using 3rd party extensions.
+2Yes this is happening to me today to, on a script that had been working fine for a very long time. Not sure what to do, this is affecting our work flow, hoping it's resolved soon!
+4Also having the same business critical issue here. Please roll back your latest deployment/PR. Your int. test failed at capturing this bug.
+4I also have this issue, I tried to use remoteFetchAsync with method POST or PUT, but this method actually called the GET method, which is totally wrong.
+9
// line 71 here
let response = await remoteFetchAsync(webhookUrl, {
method: 'POST',
body: JSON.stringify(dataJSON),
headers: {
'Content-Type': 'application/json',
},
});
Me also, the code worked before until now.
On my side, I found only the account with the Owner permission still works, but the error occurs on the other account permission types e.g. Creator/Editor/...
*** Update 1 *** It now shown this error regardless of account permission, just after I re-login the owner account now face the same issue as everyone. ***
*** Update 2 *** SOLUTION !! - Migrate extension script to automation script, then we could run away from this problem *** See how 👉 Re: remoteFetchAsync not working - Page 2 - Airtable Community
+4
// line 71 here
let response = await remoteFetchAsync(webhookUrl, {
method: 'POST',
body: JSON.stringify(dataJSON),
headers: {
'Content-Type': 'application/json',
},
});
Me also, the code worked before until now.
On my side, I found only the account with the Owner permission still works, but the error occurs on the other account permission types e.g. Creator/Editor/...
*** Update 1 *** It now shown this error regardless of account permission, just after I re-login the owner account now face the same issue as everyone. ***
*** Update 2 *** SOLUTION !! - Migrate extension script to automation script, then we could run away from this problem *** See how 👉 Re: remoteFetchAsync not working - Page 2 - Airtable Community
I have an owner account, but the error still occurs on my side saddly.
+9I have an owner account, but the error still occurs on my side saddly.
Ahh, it worked on the Owner account until I do logout. Then login back give me error same as everyone now.
*** Update *** Runaway solution here 👉 Re: remoteFetchAsync not working - Page 2 - Airtable Community
+4I tried to use a bypass CORS extension (e.g https://chrome.google.com/webstore/detail/allow-cors-access-control/lhobafahddgcelffkeicbaginigeejlf) (or enable CORS on API server), then update the script to use fetch instead of remoteFetchAsync. This is a workaround solution while waiting for AirTable to fix this.
+3I tried to use a bypass CORS extension (e.g https://chrome.google.com/webstore/detail/allow-cors-access-control/lhobafahddgcelffkeicbaginigeejlf) (or enable CORS on API server), then update the script to use fetch instead of remoteFetchAsync. This is a workaround solution while waiting for AirTable to fix this.
We have same problem and this fixed it for us. thank you so much for posting you saved us a lot of pain
+2Hello,
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,
+2Does 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)?
+9I tried to use a bypass CORS extension (e.g https://chrome.google.com/webstore/detail/allow-cors-access-control/lhobafahddgcelffkeicbaginigeejlf) (or enable CORS on API server), then update the script to use fetch instead of remoteFetchAsync. This is a workaround solution while waiting for AirTable to fix this.
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.
+2same problem here. using fetch is not possible for us because we can't change cors settings. hope this gets solved very soon.
+3yea 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
+2Does 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)?
@quyvo wrote:I tried to use a bypass CORS extension (e.g https://chrome.google.com/webstore/detail/allow-cors-access-control/lhobafahddgcelffkeicbaginigeejlf) (or enable CORS on API server), then update the script to use fetch instead of remoteFetchAsync. This is a workaround solution while waiting for AirTable to fix this.
^^^^^
@quyvo's temporary workaround will work for most cases if you only need to test your script, there are some services that will still block you although you are using fetch and the allow cors chrome plugin is on (I have a gcloud run service that I can get the workaround to work and fetch the data from but when I need to make another call to a gcloud function I still get an error).
Did anyone hear from Airtable's support? currently still waiting for an answer about the issue.
**** Update
Airtable support responded:
Hi there,
We’re incredibly sorry for the trouble - Airtable is currently experiencing problems with its API, and our engineers are actively working on the issue. We know that you rely on Airtable, and we sincerely apologize for the disruption that this issue is causing you.
We will be in touch as soon as we have any updates! Thanks so much for your patience.
Best,
The Airtable Support Team
+6Please Fix ASAP, this is causing business critcal errors
+9
@quyvo wrote:I tried to use a bypass CORS extension (e.g https://chrome.google.com/webstore/detail/allow-cors-access-control/lhobafahddgcelffkeicbaginigeejlf) (or enable CORS on API server), then update the script to use fetch instead of remoteFetchAsync. This is a workaround solution while waiting for AirTable to fix this.
^^^^^
@quyvo's temporary workaround will work for most cases if you only need to test your script, there are some services that will still block you although you are using fetch and the allow cors chrome plugin is on (I have a gcloud run service that I can get the workaround to work and fetch the data from but when I need to make another call to a gcloud function I still get an error).
Did anyone hear from Airtable's support? currently still waiting for an answer about the issue.
**** Update
Airtable support responded:
Hi there,
We’re incredibly sorry for the trouble - Airtable is currently experiencing problems with its API, and our engineers are actively working on the issue. We know that you rely on Airtable, and we sincerely apologize for the disruption that this issue is causing you.
We will be in touch as soon as we have any updates! Thanks so much for your patience.
Best,
The Airtable Support Team
I found people in this threads are facing the same problem, but the work around can be done based on your environment.
Case 1. remoteFetchAsync was inside your automation script. Here you can switch from remoteFetchAsync to fetch, then it will be solved.
Case 2. remoteFetchAsync was inside your extension script. In this case, the script will be run using a browser, so you will still not be able to switch to fetch as and Airtable frontend still block you with CORS related issue. So, you will need to migrate your extension script to automation script.
Case 2 How?
You will need to create an automation trigger e.g. when a record is updated (maybe a check box) -> then run your migrated script. Also, if you need inputs, you need to change input.recordAsync() to input.config()
Well, this way solves the problem on my side completely.
But wait?? why we need to do these ourselves?
Airtable Support team please wakeup, your morning is burning!! 😅
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
