Skip to main content

I am working with a Zapier Table and suddenly all of my Zaps that include the “Update Table” action stopped working for a specific table showing this error: 

 

Failed to create a record in Zapier Tables

Error code 404: Table 01JSM8X2BE8YK5918ZDJB16ZXF not found (table:notfound)

 

What’s weird about this is that I don’t own a table with the ID shown in the error message. The previous selected table has a different ID. Also when configuring the action for my zap, it’s only showing me the Table ID and Record ID to be updated. All other fields don’t pop up - but when I select another table it’s working without any problems showing all fields. I also tried duplicating the table, which didn’t help.

 

As Trigger I used “New Record” - which is working fine.

 

Additional info that might help:

  • The table includes 48 different fields - too much data?
  • I renamed the table at some point - does that affect the ID?
  • My table includes 3 different views
  • The Table is connected to a Zapier Interface

 

Thanks for your help!

 

 

Hello ​@marvinpamo ,
 

This might be a Zapier cache/reference mismatch due to a renamed table or corrupted config in the “Update Table” action step.
 

Try re-selecting the Table in the action step and see if it repopulate the fields. If re-selecting doesn’t work, delete and re-add the “Update Table” action and select the correct table.

If none of the above works, Zapier may still cache it internally, contact Zapier support and ask them to clear or reset the Zap’s internal table reference.


Hi there, ​@marvinpamo 👋

Did re-selecting the table as Sync9-Solutions suggested do the trick? Or did you figure out a different solution?

Want to make sure this gets sorted, please let us know how it’s going! 🙏


Hello ​@Sync9-Solutions ​@SamB ,

thanks for the help! Re-selecting or re-adding the action step unfortunately didn’t solve the problem. My zaps are actually working again and I’m still in contact with the Zapier tech support to investigate this further.

According to what we’ve witnessed, it seems I had some filters applied to the main table which caused the error, and after removing them, it took some time for the Zap to start working again.

Will send an update as soon as I receive more info about this!


Thanks for the update, ​@marvinpamo! Glad to hear things are working again—and good call to reach out to our Support team. Looking forward to hearing what they find. 😁