Apps Script BigQuery calls fail when the API isnt enabled on the project

TL;DR

The accepted fix: the new copy was bound to a different Cloud project, and the BigQuery API had to be enabled on that project via Advanced Google Services and the Cloud console.

Fix

When Apps Script throws 'project not found and cannot be used for API calls', open Resources, Advanced Google Services and follow the link to the Cloud console for the bound project, then enable the API there. Duplicated scripts bind to new projects silently, so the API enablement doesnt carry over.

Context: Stack Overflow #43234769 (accepted answer, 14 votes): duplicating a sheet that called the BigQuery API produced 'Project not found and cannot be used for API calls'. The accepted fix: the new copy was bound to a different Cloud project, and the BigQuery API had to be enabled on that project via Advanced Google Services and the Cloud console.

Matched source

Source: Published skill Original query: "Apps Script BigQuery calls fail when the API isnt enabled on the project" Key terms: apps, bigquery, calls, enabled, fail, isnt, project, script

When to use this

• Use this when your task, error, or question matches the title above and the setup in the Fix section.

When not to use this

• Skip it when the error text, tool, or situation is different. Forcing a mismatched fix usually costs more time than searching again.

Compatibility

The original write-up does not pin tool versions. Treat the commands and UI paths above as reflecting the author's setup, and check your tool's own docs if your version looks different.

Source: Stack Overflow #43234769 (accepted answer, 14 votes): duplicating a sheet that called the BigQuery API produced 'Project not found and cannot be used for API calls'. The accepted fix: the new copy was bound to a different Cloud project, and the BigQuery API had to be enabled on that project via Advanced Google Services and the Cloud console.

Verified resolution: When Apps Script throws 'project not found and cannot be used for API calls', open Resources, Advanced Google Services and follow the link to the Cloud console for the bound project, then enable the API there. Duplicated scripts bind to new projects silently, so the API enablement doesnt carry over.

Source URL: https://stackoverflow.com/questions/43234769/project-project-id-is-not-found-and-cannot-be-used-for-api-calls