Your a legend! We are back up.

Thank you siriwat.

Hey everyone, we wanted to acknowledge that the team is aware of the error when using RemoteFetchAsync() and are currently investigating the issue. We apologize for the inconvenience that this may have caused and hope to have more information to provide soon.

Thank you Jessy, I greatly appreciate your acknowledgment of the error. 

Many thanks, 

Mauro 

We have a time critical email we need to send to 500+ users via the SendGrid extension right now. What is the ETA for this?

Same here business cirtical issue

hi @wheels_2go ,
I also encountered this issue a few hours ago. I solved it by replacing the name of the function, changing it from remoteFetchAsync to fetch. I believe that Airtable made a change, aligning the fetch function in the automations, with the same function on extensions (they used to have two different names with the extensions one being remoteFetchAsync, now they are both called fetch). Hope this helps!

Website: alessiomonino.com
Calendly: https://alessiomonino.com/contact
Email: alessio.monino@gmail.com

@Alessio_Monino, I don't believe Airtable has made a change yet. The automations are able to use fetch because they don't have CORS restrictions.

That said, confirming that moving my extension code to an automation script, replacing remoteFetchAsync with fetch, plus removing references to session (since automations don't have access), temporarily resolved this issue for me as well.

Definitely is linked to a recent update on the Airtable side. The reply I got was super vague though, and this has brought several of our bases to a screeching halt.

Same issue here., critical problem for us too, remoteFetchAsync() fails when called from Extension script.

I temporarily fixed using "fetch" instead, but I concern it can cause CORS issue.

Not savvy over here, how would I implement this fetch fix with the Sendgrid extension?

You can’t implement the fix with the extension as you cannot modify how the extension is making its calls. We send transactional email thru send gris out of Airtable all the time and they’re always done via automaton - if you tell me a little more about what you’re trying to send I might be able to help.

Is this a marketing campaign or just a dynamic template with some fields from your base merged in?

Oh that might be a good solution - it's just the basic sendgrid template with fields. 

I'll try the automated send email function for now to get the emails out. 

Because this is so widespread, would it be possible to make this visible on the Airtable Status page? (status.airtable.com)
This is something many of us are paying attention to and is practically "system down" in our particular situation.

No, I mean that I use a script step in an automation to do what you're describing through SendGrid - the send email automation step has really severe limits and will more than likely not work for your use case. You'll have to construct the send call with fetch() (which should work) and match it to your template. Can you send me a list of your template variables? I'll adapt my function to include your variables and give you some notes on how to complete the setup if you'd like.

In my experience status.airtable.com rarely actually reports outages like this. It's pretty frustrating actually 🙂

Same issue as well. Not sure what to do since I don't want to create a custom solution for just this if it gets resolved, but also this is stopping us from getting work done...

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.

Thank you for the fix. It must have been tough getting this out with everything that is happening.

I did have to reload Airtable to get my scripting extension to work.

The problem is not resolved when it comes to the Airtable-provided SendGrid extension unless you refresh the Airtable page, as pointed out by @kuovonne. Would be helpful if you included that instruction.

Nothing was changed. The problem is not solved!

It seems to be working for me