Skip to main content
Question

Field agent error: Unable to extract content from attachment(s)

  • October 31, 2025
  • 6 replies
  • 150 views

nroshak
Forum|alt.badge.img+9

I’m getting the error “Something went wrong: Unable to extract content from attachment(s)” when I’m running a field agent on an attachment field.

The attachments are all PDFs. I’ve personally reviewed them all (there are only 17 rows) and they all render just fine in multiple PDF viewers, including Airtable’s.

This is not a consistent error. Using some AI models I do not get the error; with other AI models I get the error on first run with one row, but running it again clears the error.

What gives? Anyone else hit this or have any insight?

-Natalka

6 replies

Mike_AutomaticN
Forum|alt.badge.img+28

Hey ​@nroshak,

This issue has been raised multiple times on the community. In fact, I stumbled upon similar issues. I don’t have a clear answer for you.. worst case scenario, you can always build a side automation on Zapier, Make, or n8n, and get the heavy lifting done with it (whilst connecting whichever model you prefer). I know this is a pain. Until we find what patterns are causing this issues, you might want to open a ticket with support (support@airtable.com).

Also, if these are documents you’d have no problem sharing, feel free to send them over to mike@automaticnation.com and I can check if the same issue is encountered on my side.

Completely different matter, but would love to have you join our Airtable Hackathon! Make sure to sign up!!

Mike, Consultant @ Automatic Nation 
YouTube Channel 


ScottWorld
Forum|alt.badge.img+35
  • Genius
  • October 31, 2025

@nroshak 

I would open a support ticket with support@airtable.com about this issue.

In the meantime, I would suggest using Make’s AI automations, as ​@Mike_AutomaticN mentioned above. Make’s built-in AI automations will enable you to do this successfully.

If you’ve never used Make before, I’ve assembled a bunch of Make training resources in this thread. For example, here is one of the ways that you could instantly trigger a Make automation from Airtable

Hope this helps!

If you have a budget and you’d like to hire the best Airtable consultant to help you with this or anything else that is Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld


Alexey_Gusev
Forum|alt.badge.img+25
  • Brainy
  • October 31, 2025

Hi,
usually in my tests default AI model ‘GPT-4’ produces less errors than others (even GPT-5 sometimes less reliable). Of course, when you want to use less AI credits, sometimes it’s wise to choose ‘low cost’ AI model, when it’s no difference between results. But in many cases change of model really make things worse.


Forum|alt.badge.img+18
  • Inspiring
  • February 10, 2026

Anyone have an update on this? I have a client for whom we’ve built major workflows that rely on these fields. They worked well in the past, but have all the sudden stopped working today. They don’t have time or budget to re-build the entire process in Make or other tool. I have submitted a support ticket for this.


Alexey_Gusev
Forum|alt.badge.img+25
  • Brainy
  • February 10, 2026

I have the same problem now in new table. Yesterday and day before it all worked OK (in other bases/tables)
Less than 10 files, quite easy prompt, default GPT model. Preview generated correct and fast, but the field itself stuck and “Analysing...”  for a long time, until “Still pending. Queued...”. 


Forum|alt.badge.img+18
  • Inspiring
  • February 10, 2026

@Alexey_Gusev Same - mine worked fine yesterday. Please submit an Airtable Support ticket for this. I believe there is a broader bug. I’m experiencing the issue across multiple bases and workspaces.