docs: parallel dbt jobs and metadata artifact upload guidance

Document contention when parallel jobs write Elementary metadata tables:
disable_dbt_artifacts_autoupload on concurrent runs and a scheduled job
using dbt run --select elementary with enable_elementary_models.

Align on-run-end hooks and reduce-on-run-end-time examples with the same
command; link to FAQ for the dbt_project.yml pattern.

Made-with: Cursor

Author: NoyaOffer

docs/cloud/guides/troubleshoot.mdx

@@ -21,6 +21,29 @@ Try following these steps to troubleshoot:
 
 </Accordion>
 
+<Accordion title="Parallel dbt jobs error when writing to Elementary metadata artifact tables">
+
+When multiple dbt jobs run in parallel, they can contend on the same Elementary metadata artifact tables.
+
+**Disable automatic metadata artifact uploads** in `dbt_project.yml`:
+
+```yaml dbt_project.yml
+vars:
+  disable_dbt_artifacts_autoupload: true
+```
+
+**Add a separate scheduled job** (daily or hourly) to upload the artifacts:
+
+```bash
+dbt run --select elementary --vars '{"enable_elementary_models": true}'
+```
+
+For the `enable_elementary_models` pattern in `dbt_project.yml`, see [Can I disable / exclude the Elementary models?](/oss/general/faq#can-i-disable-exclude-the-elementary-models). For more context, see [on-run-end hooks](/data-tests/dbt/on-run-end_hooks), [Reduce on-run-end time](/data-tests/dbt/reduce-on-run-end-time), and [Dev / prod configuration](/cloud/guides/dev-prod-configuration).
+
+Let us know if you run into anything — start a chat from the Elementary UI or reach us on [Slack](https://elementary-data.com/community).
+
+</Accordion>
+
 <Accordion title="Column information cannot be retrieved">
 
 This error can happen because of a few reasons:

docs/data-tests/dbt/on-run-end_hooks.mdx

@@ -70,7 +70,7 @@ vars:
   disable_dbt_artifacts_autoupload: true
 ```
 
-2. Make sure to run `dbt run --select edr.dbt_artifacts` upon merging PRs.
+2. Make sure to run `dbt run --select elementary --vars '{"enable_elementary_models": true}'` upon merging PRs.
 
 </Accordion>
 
@@ -100,9 +100,7 @@ vars:
 ```
 
 <Warning>
-  If you disable the artifacts autoupload, we recommend your run `dbt run
-  --select elementary.edr.dbt_artifacts` every time you deploy changes to your
-  project.
+  If you disable the artifacts autoupload, we recommend you run `dbt run --select elementary --vars '{"enable_elementary_models": true}'` every time you deploy changes to your project.
 </Warning>
 
 #### Disable result models updates

docs/oss/general/troubleshooting.mdx

@@ -210,19 +210,27 @@ If you want the Elementary UI to show data for a longer period of time, use the
 
 
 
-<Accordion title="Error when trying to run parallel dbt jobs">
+<Accordion title="Parallel dbt jobs error when writing to Elementary metadata artifact tables">
 
-When writing to the `dbt_artifacts` tables in the Elementary schema, data is deleted and reinserted. Running parallel jobs through an orchestrator can lead to errors, as multiple jobs may attempt to modify the same tables simultaneously. 
-To prevent this, you should:
-1. [Disable the on-run-end hooks](/oss/general/faq#can-i-disable-the-on-run-end-hooks-or-results-uploading)
-2. [Exclude the Elementary models](/oss/general/faq#can-i-disable-exclude-the-elementary-models)
+When multiple dbt jobs run in parallel, they can contend on the same Elementary metadata artifact tables.
 
-For scheduled updates to `dbt_artifacts` (e.g., a daily job), run:
+**Disable automatic metadata artifact uploads** in `dbt_project.yml`:
 
+```yaml dbt_project.yml
+vars:
+  disable_dbt_artifacts_autoupload: true
 ```
+
+**Add a separate scheduled job** (daily or hourly) to upload the artifacts:
+
+```bash
 dbt run --select elementary --vars '{"enable_elementary_models": true}'
 ```
 
+For the `enable_elementary_models` pattern in `dbt_project.yml`, see [Can I disable / exclude the Elementary models?](/oss/general/faq#can-i-disable-exclude-the-elementary-models). For more context, see [on-run-end hooks](/data-tests/dbt/on-run-end_hooks) and [Reduce on-run-end time](/oss/guides/reduce-on-run-end-time).
+
+Let us know if you run into anything — we’re responsive on [#community-support](https://elementary-community.slack.com/archives/C02CTC89LAX).
+
 </Accordion>
 
 

docs/snippets/guides/reduce-on-run-end-time.mdx

@@ -28,9 +28,11 @@ vars:
 When you need to update metadata (e.g., after schema changes or adding new models), upload artifacts either manually or via a recurring job (e.g., daily):
 
 ```bash
-dbt run --select elementary.edr.dbt_artifacts
+dbt run --select elementary --vars '{"enable_elementary_models": true}'
 ```
 
+For the `enable_elementary_models` pattern in `dbt_project.yml`, see [Can I disable / exclude the Elementary models?](/oss/general/faq#can-i-disable-exclude-the-elementary-models).
+
 <Info>
 Metadata artifacts only need to be uploaded when your project structure changes (new models, tests, sources, etc.). For most runs, you only need run results, which are much faster to upload.
 </Info>