Request for timeout increase to complete build which keeps failing due to 'Timing Out' after clearing cache

Hello,
Following a cache clear, we are encountering Build Timeouts when trying to rebuild our site with Site ID: 9576dc55-d9fb-423f-9634-99db001197a4 (Netlify Domain: ce23.netlify.app)

We are requesting a Timeout Limit increase so that we will be able to rebuild and restore the cache to use for subsequent builds

Build Settings Screenshot

This is a link to the failed deployment:

SNIPPET of Build Log below:

10:29:34 AM: success extract queries from components - 19.632s
10:29:34 AM: warning The GraphQL query in the non-page component “/opt/build/repo/src/templates/page/events/no-events/index.js” will not be run.
10:29:34 AM: warning The GraphQL query in the non-page component “/opt/build/repo/src/templates/page/opportunities/no-opportunities/index.js” will not be run.
10:29:34 AM: warning The GraphQL query in the non-page component “/opt/build/repo/src/templates/page/careers/no-careers/index.js” will not be run.
10:29:34 AM: Exported queries are only executed for page components. It’s possible you’re trying to create pages in your gatsby-node.js and that’s failing for some reason.
10:29:34 AM: If the failing component is a regular component and not intended to be a page component, you generally want to use “useStaticQuery” (Querying Data in Components with the useStaticQuery Hook | Gatsby) instead of exporting a page query.
10:29:35 AM: If you’re more experienced with GraphQL, you can also export GraphQL fragments from components and compose the fragments in the Page component query and pass data down into the child component (Using GraphQL Fragments | Gatsby)
success write out redirect data - 0.613s
10:29:41 AM: success Build manifest and related icons - 5.976s
10:29:41 AM: success onPostBootstrap - 5.983s
10:29:41 AM: info bootstrap finished - 2723.937s
10:29:45 AM: success write out requires - 3.613s
10:33:18 AM: success Building production JavaScript and CSS bundles - 213.475s
10:44:13 AM: Failed during stage ‘building site’: Command did not finish within the time limit
10:44:13 AM: Execution timed out after 1h0m0.136391494s
10:44:13 AM: Failing build: Failed to build site
10:44:14 AM: Finished processing build request in 1h1m18.616s

Looking forward to your assistance.
Prince

hi your build timeout is already set at 2 hours Have you re-deployed this site?

Not since I contacted you. Will redeploy again now.

The deploy was successful - Thanks.
Just to clarify did you increase it to 2 hours following my request? Or was it already set to 2 hours?

It would be hard to check now, but as long as you’re unblocked, I guess it’s resolved?