# Run stops after 300s regardless to profiles.yml configuration. Bigquery plugin

**URL:** <https://discourse.getdbt.com/t/run-stops-after-300s-regardless-to-profiles-yml-configuration-bigquery-plugin/10175>\
**Category:** Help\
**Tags:** bigquery\
**Created:** [October 1, 2023, 12:08pm UTC](https://discourse.getdbt.com/t/run-stops-after-300s-regardless-to-profiles-yml-configuration-bigquery-plugin/10175 "2023-10-01T12:08:17Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![shani.cohen](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.getdbt.com/shani.cohen/32/3046_2.png) [@shani.cohen](https://discourse.getdbt.com/u/shani.cohen)\
**Post date:** [October 1, 2023, 12:08pm UTC](https://discourse.getdbt.com/t/run-stops-after-300s-regardless-to-profiles-yml-configuration-bigquery-plugin/10175/1 "2023-10-01T12:08:17Z")

</div>

> **[BigQuery setup | dbt Developer Hub](https://docs.getdbt.com/docs/core/connect-data-platform/bigquery-setup#timeouts-and-retries)**
>
> Read this guide to learn about the BigQuery warehouse setup in dbt.

Hey all,

im trying to run a large model and I’m running into a  
_ **“Runtime Error in model… Query exceeded configured timeout of 300s”** _  
\*\*when trying to run a specific file.

This happens after about **5 minutes** ,

 ![image](https://us1.discourse-cdn.com/flex020/uploads/getdbt/original/2X/9/975770da8501b7044bcb2b995192bbf4e28b095e.jpeg)

but my timeout in the profiles.yml file is defined to be 10 minutes:  
_ **job\_execution\_timeout\_seconds: 600** _

* * *

I’ve updated my version:  
Core:

- installed: 1.6.4
- latest: 1.6.4 - Up to date!

Plugins:

- bigquery: 1.6.6 - Up to date!

I’ve also tried to reduce the “job\_execution\_timeout\_seconds” to be 60 seconds to check if it will stop after 60 seconds but it still runs about 5 minutes and then stops.

---

<div class="post-metadata">

**Author:** ![brunoszdl](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.getdbt.com/brunoszdl/32/4113_2.png) [@brunoszdl](https://discourse.getdbt.com/u/brunoszdl)\
**Post date:** [October 3, 2023, 12:20am UTC](https://discourse.getdbt.com/t/run-stops-after-300s-regardless-to-profiles-yml-configuration-bigquery-plugin/10175/2 "2023-10-03T00:20:00Z")

</div>

Never had this problem ☹

But what I would try:

In the docs you have this:

> The `job_execution_timeout_seconds` represents the number of seconds to wait for the [underlying HTTP transport](https://cloud.google.com/python/docs/reference/bigquery/latest/google.cloud.bigquery.job.QueryJob#google_cloud_bigquery_job_QueryJob_result). It _doesn’t_ represent the maximum allowable time for a BigQuery job itself. So, if dbt-bigquery ran into an exception at 300 seconds, the actual BigQuery job could still be running for the time set in BigQuery’s own timeout settings.

So, maybe try changing the `default_query_job_timeout_ms` in BigQuery’s own settings

> **[Manage default configurations  |  BigQuery  |  Google Cloud](https://cloud.google.com/bigquery/docs/default-configuration)**

---

<div class="post-metadata">

**Author:** ![bjoernp](https://avatars.discourse-cdn.com/v4/letter/b/a587f6/32.png) [@bjoernp](https://discourse.getdbt.com/u/bjoernp)\
**Post date:** [February 13, 2024, 2:42pm UTC](https://discourse.getdbt.com/t/run-stops-after-300s-regardless-to-profiles-yml-configuration-bigquery-plugin/10175/3 "2024-02-13T14:42:53Z")

</div>

Has anyone ever found a resolution to this? I have a similar problem. I have configured no timeouts, and even set job\_retries to 5, but I get regular query timeouts after 900s, and dbt doesn’t retry even once. These are normal query jobs.

I’ve also checked to make sure it’s not BigQuery itself, and the job actually continue running and complete just fine. So I’m really wondering what I need to do to make dbt wait indefinitely.

For reference, here’s the output of `dbt debug`:

```auto
13:42:03 Running with dbt=1.7.7
13:42:03 dbt version: 1.7.7
13:42:03 python version: 3.11.7
13:42:03 python path: *****
13:42:03 os info: macOS-14.3.1-x86_64-i386-64bit
13:42:04 Using profiles dir at *****
13:42:04 Using profiles.yml file at *****
13:42:04 Using dbt_project.yml file at *****
13:42:04 adapter type: bigquery
13:42:04 adapter version: 1.7.4
13:42:04 Configuration:
13:42:04 profiles.yml file [OK found and valid]
13:42:04 dbt_project.yml file [OK found and valid]
13:42:04 Required dependencies:
13:42:04 - git [OK found]

13:42:04 Connection:
13:42:04 method: oauth
13:42:04 database: *****
13:42:04 execution_project: *****
13:42:04 schema: *****
13:42:04 location: EU
13:42:04 priority: interactive
13:42:04 maximum_bytes_billed: None
13:42:04 impersonate_service_account: None
13:42:04 job_retry_deadline_seconds: None
13:42:04 job_retries: 5
13:42:04 job_creation_timeout_seconds: None
13:42:04 job_execution_timeout_seconds: None
13:42:04 keyfile: None
13:42:04 timeout_seconds: None
13:42:04 refresh_token: None
13:42:04 client_id: None
13:42:04 token_uri: None
13:42:04 dataproc_region: None
13:42:04 dataproc_cluster_name: None
13:42:04 gcs_bucket: None
13:42:04 dataproc_batch: None
13:42:04 Registered adapter: bigquery=1.7.4
13:42:06 Connection test: [OK connection ok]

13:42:06 All checks passed!

```

---

<div class="post-metadata">

**Author:** ![bjoernp](https://avatars.discourse-cdn.com/v4/letter/b/a587f6/32.png) [@bjoernp](https://discourse.getdbt.com/u/bjoernp)\
**Post date:** [February 13, 2024, 2:54pm UTC](https://discourse.getdbt.com/t/run-stops-after-300s-regardless-to-profiles-yml-configuration-bigquery-plugin/10175/4 "2024-02-13T14:54:08Z")

</div>

Ok, this seems to be a known bug in the `dbt-bigquery`, see [here](https://github.com/dbt-labs/dbt-bigquery/issues/1081).

---

<div class="post-metadata">

**Author:** ![atul.raut](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.getdbt.com/atul.raut/32/3017_2.png) [@atul.raut](https://discourse.getdbt.com/u/atul.raut)\
**Post date:** [May 16, 2024, 4:22pm UTC](https://discourse.getdbt.com/t/run-stops-after-300s-regardless-to-profiles-yml-configuration-bigquery-plugin/10175/5 "2024-05-16T16:22:43Z")

</div>

I had faced same issue where model timeout after 300 seconds.  
**Solution**  
when we setup a Bigquery connection for a dbt project using key authentication - There is a J **ob execution timeout seconds** setting available which is by default set to 300 seconds.

If the dbt cloud project is already setup - Then

1. go to settings \>\> project \>\> dbt Project Name
2. Click on Bigquery connection link
3. edit Job execution timeout seconds setting option

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/getdbt/original/1X/a7a7ca1fe379aaf90952b0e13118a817babcd14f.png) [@system](https://discourse.getdbt.com/u/system)\
**Post date:** [November 13, 2024, 9:36pm UTC](https://discourse.getdbt.com/t/run-stops-after-300s-regardless-to-profiles-yml-configuration-bigquery-plugin/10175/6 "2024-11-13T21:36:51Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.