gatsby-source-contentful Rate Limit Issues and Missing Content in Production Build (gatsby-source-contentful v7.22.0, Gatsby v4.22.0)

[avieira01]

Description:

We are facing a blocking issue in our production pipeline with gatsby-source-contentful version 7.22.0 and Gatsby v4.22.0.

Key Issues:

Rate Limit Problems: We're encountering rate limit issues from Contentful, but there are no logs indicating these problems in the production build. This makes it difficult to identify when and where we hit the rate limit.

Missing Content: As a result of these rate limit problems, some of our production builds are missing content. The missing content is not appearing consistently, which is affecting our deployments.

Questions:

Is there a way to set a rate of requests within gatsby-source-contentful to avoid hitting the rate limits?
Can the logging for rate limit issues be improved in production builds so we can more easily identify when we’re being throttled?
Context:
We know that these versions are outdated, but we are in the process of upgrading. However, this issue is blocking our pipeline and needs to be resolved to allow us to proceed.