Help

Re: remoteFetchAsync not working

Solved
Jump to Solution
3744 2
cancel
Showing results for 
Search instead for 
Did you mean: 
wheels_2go
4 - Data Explorer
4 - Data Explorer

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?

1 Solution

Accepted Solutions
Jessy_Hu
Airtable Employee
Airtable Employee

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.

See Solution in Thread

46 Replies 46
eejeremy
4 - Data Explorer
4 - Data Explorer

Yes 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!

spaceman
4 - Data Explorer
4 - Data Explorer

Also having the same business critical issue here. Please roll back your latest deployment/PR. Your int. test failed at capturing this bug.

ivalles
4 - Data Explorer
4 - Data Explorer

Also having this critical issue. It's stopping our workflow.

quyvo
5 - Automation Enthusiast
5 - Automation Enthusiast

I 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.

siriwat
6 - Interface Innovator
6 - Interface Innovator

siriwat_1-1694663962929.png

 

// 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

quyvo
5 - Automation Enthusiast
5 - Automation Enthusiast

I have an owner account, but the error still occurs on my side saddly.

siriwat
6 - Interface Innovator
6 - Interface Innovator

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

aproli90
4 - Data Explorer
4 - Data Explorer

Any updates on this issue so far? Business critical issue for us. 

quyvo
5 - Automation Enthusiast
5 - Automation Enthusiast

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.