Netlify deployment failing due to gatsby-source-airtable plugin error

Other Questions Airtable
1

Hey folks, I’m having trouble with my Gatsby project. It works fine locally, but when I try to deploy on Netlify, it crashes. The error message says something about gatsby-source-airtable messing up during the sourceNodes part.

Here’s what I’ve got in my gatsby-config.js for Airtable:

{
  resolve: `gatsby-source-airtable`,
  options: {
    apiKey: process.env.AIRTABLE_API_KEY,
    concurrency: 5,
    tables: [
      {
        baseId: baseId,
        tableName: `Company`,
        queryName: true,
        tableLinks: [`Discounts`, `Company_Logos`],
      },
      // ... other tables ...
    ],
  },
},

I’m using these versions:

  • gatsby-source-airtable: 2.1.1
  • react: 16.12.0
  • gatsby-source-graphql: 2.7.6

I’ve already tried deleting node_modules and the yarn.lock file and rebuilding. Nothing seems to work, so I’m hoping someone can shed some light on what might be going wrong. Any ideas would be greatly appreciated. Thanks!

2

yo, have u tried clearin ur netlify cache? sometimes that helps. also, double-check ur airtable API key in netlify’s environment variables. if that don’t work, maybe try usin a different version of gatsby-source-airtable plugin. good luck man!

3

Have you considered the possibility of a rate limiting issue with the Airtable API? I encountered a similar problem when deploying to Netlify. The solution that worked for me was implementing a custom plugin to handle rate limiting.

Here’s what I did:

  1. Created a custom plugin that wraps the Airtable API calls.
  2. Implemented exponential backoff for retries on rate limit errors.
  3. Added this custom plugin to my gatsby-config.js instead of the standard gatsby-source-airtable.

This approach significantly improved the stability of my builds on Netlify. It might be worth exploring if the other suggestions haven’t resolved your issue.

Additionally, double-check that your Airtable base structure hasn’t changed since your last successful build. Sometimes, unexpected schema changes can cause deployment failures.

4

I’ve run into similar issues with Gatsby and Airtable before. One thing that helped me was explicitly setting the Airtable API key in Netlify’s environment variables. Sometimes, even if it’s in your .env file locally, it doesn’t translate to the Netlify deployment.

Another trick that worked for me was increasing the concurrency in the gatsby-source-airtable options. Try bumping it up to 10 or even 20, especially if you have a lot of data or complex relationships between tables.

Lastly, check if there are any discrepancies between your local and Netlify Node.js versions. I once spent hours debugging only to realize my local setup was using a newer Node version than what Netlify defaulted to.

If none of these work, you might want to try downgrading gatsby-source-airtable to version 2.0.0. I’ve found older versions sometimes play nicer with certain Gatsby setups.