What causes DbtCloudJobTriggerError?

The dbt Cloud API service token used by the external orchestrator expired, was deleted, or has insufficient permissions for the target account and project. The job ID in the API trigger URL or payload references a job in a different dbt Cloud account or project than the one the token authorizes. The request payload does not include a required field such as cause or steps_override, causing a 400 Bad Request response

How do I fix DbtCloudJobTriggerError?

Step 1: Test the API token independently: curl -H 'Authorization: Token ' https://cloud.getdbt.com/api/v2/accounts/ / and verify a 200 response.. Step 2: Confirm the job ID is correct and belongs to the account authorized by the token: GET /api/v2/accounts/ /jobs/ /.. Step 3: Verify the trigger payload includes at minimum the 'cause' field: {"cause": "triggered by orchestrator"}.. Step 4: Check the dbt Cloud audit log to see if the trigger request was received and what error was returned at the API layer.

High severityconfiguration

Power BI Refresh Error:
DbtCloudJobTriggerError

What does this error mean?

An external system failed to trigger a dbt Cloud job via the dbt Cloud API because the request was rejected due to an invalid API token, a missing or incorrect job ID, or a malformed request payload.

Common causes

1The dbt Cloud API service token used by the external orchestrator expired, was deleted, or has insufficient permissions for the target account and project
2The job ID in the API trigger URL or payload references a job in a different dbt Cloud account or project than the one the token authorizes
3The request payload does not include a required field such as cause or steps_override, causing a 400 Bad Request response

How to fix it

1Step 1: Test the API token independently: curl -H 'Authorization: Token <your_token>' https://cloud.getdbt.com/api/v2/accounts/<account_id>/ and verify a 200 response.
2Step 2: Confirm the job ID is correct and belongs to the account authorized by the token: GET /api/v2/accounts/<account_id>/jobs/<job_id>/.
3Step 3: Verify the trigger payload includes at minimum the 'cause' field: {"cause": "triggered by orchestrator"}.
4Step 4: Check the dbt Cloud audit log to see if the trigger request was received and what error was returned at the API layer.

Frequently asked questions

Which dbt Cloud API scope is needed to trigger a job?

The service token must have the 'Job Admin' or 'Developer' account permission. Read-only tokens cannot trigger jobs.

Can I use the dbt Cloud API to trigger a job in a different account?

No. Each service token is scoped to a single dbt Cloud account. To trigger jobs in multiple accounts, you need separate tokens — one per account.