Error: Invalid workspace selection: "failed to find workspace" in the backend

Not specified by the original author.

TL;DR

Terraform is pointed at a workspace that does not exist in your backend (Terraform Cloud/Enterprise, or a local name you never created). Create the workspace where the backend expects it, or fix the workspace name in your cloud/backend block.

The error

Error: Invalid workspace selection
Terraform failed to find workspace "grafana" in organization wifihaven.

Steps to fix

1. Identify where the name comes from: the cloud { workspaces { name = "..." } } block, backend config, or terraform workspace select.

   • Expected: you find the exact expected name.

2. Check what exists: in Terraform Cloud, open the organization and list workspaces; locally, run terraform workspace list.

   • Expected: the expected name is absent, confirming the diagnosis.

3. Either create the workspace (matching execution mode and VCS settings), or correct the name in config and run terraform init -reconfigure.

   • Expected: init selects the workspace successfully.

4. Re-run the failed command.

   • Expected: plan/apply proceeds.

When to use this

• terraform init fails with Invalid workspace selection after a backend migration, a fresh checkout, or a renamed workspace.

When NOT to use this

• A typo in terraform workspace select [name] on a local backend is fixed by terraform workspace new [name] or selecting the right one. Do not create production workspaces casually to silence this.

Compatibility

• All Terraform versions; Terraform 1.16+ additionally errors if the selected workspace becomes invalid out-of-band.

Root cause

The backend resolves the workspace name at init. If the workspace was never created, was deleted, or the config points at the wrong org/name after a migration, resolution fails before any state is touched.

Edge cases

• cloud block with tags selects workspaces by tag; a missing tag match fails the same way.
• Local backend: terraform workspace select with TF_WORKSPACE env var set can surprise you; check the env.
• After creating the workspace, the first apply starts from empty state; confirm that is what you want before applying.

wifihaven/wifihaven#1440 is a real incident: after an HCP Terraform remote-backend migration, every CI run failed with "Error: Invalid workspace selection. Terraform failed to find workspace \"grafana\" in organization wifihaven." The root cause was a cloud {} block pointing at a workspace that did not exist in HCP Terraform; the fix was creating the workspace in the org with matching settings (execution mode, no VCS attachment) and re-running. Terraform 1.16 also hardened this path, now erroring when an invalid workspace name becomes selected out-of-band.

Not specified by the original author.

Fix Notion OAuth failing with restrictedtoworkspace

TL;DR

The Notion integration is restricted to a specific workspace - either it is an internal integration, which by design installs only in its home workspace, or the target workspace blocks outside integrations. Install it in the allowed workspace, or convert it to a public integration and complete Notion's review for cross-workspace distribution. The workspace admin decides which path applies.

The error

OAuth callback error: "restricted_to_workspace"
The integration cannot be installed in this workspace

Use this skill

Agent? Search Vectle for this error:

curl -s "https://vectle.com/api/v1/search?q=notion%20oauth%20restricted_to_workspace%20install%20error"

Fix it

Step 1: Check the integration type

Open notion.so/my-integrations, select the integration, and check whether it is internal or public.

Expected: the type is confirmed. Internal integrations can only ever install in their home workspace; that restriction is not a bug.

Step 2: Install in the correct workspace if internal is fine

Have a workspace owner of the home workspace add the integration under Settings / Connections.

Expected: the install succeeds there. If the product only ever serves one workspace, stop here.

Step 3: Convert to public for multi-workspace distribution

In the integration settings, change the distribution to public and submit it for Notion's review.

Expected: after approval, the integration installs in any workspace. Plan for review time; it is not instant.

Step 4: Check the target workspace's integration policy

In the target workspace's Settings, confirm whether workspace owners allow public integrations or require approval for each one.

Expected: the policy allows the install, or the approval request is submitted. A workspace-level block overrides everything else.

Step 5: Retry the OAuth flow from the right workspace

Start the OAuth flow while acting in the correct workspace context and complete the authorization.

Expected: authorization completes and the token works.

When this applies

• OAuth fails with restrictedtoworkspace
• The integration installs in one workspace but not another
• Distributing a Notion integration to customer workspaces

When it doesn't

• The error is invalid authorization code (code reuse or expiry)
• The redirect URI mismatches (app config issue)
• API calls fail after a successful install (capability or permission issue)

Compatibility

Notion API OAuth 2.0, internal vs public integrations.

Variant phrasings

notion integration restricted to workspace

Check the integration type first; the fix depends entirely on internal vs public.

notion oauth error restrictedtoworkspace

The error names the restriction. Match the distribution model to where it must install.

Why it happens

Notion scopes internal integrations to a single workspace by design: they are meant for first-party, single-workspace use. Cross-workspace installation requires the public distribution model plus Notion's review. The error fires whenever the install target falls outside the integration's allowed distribution, which is working as intended.

Edge cases

• Only workspace owners can install integrations; members hit a permissions wall that looks similar
• Review turnaround for public integrations varies; do not promise customers a date
• Duplicating an internal integration per workspace is a common workaround for a handful of workspaces

If it still fails

• Capture the exact timestamp, the username, and the full error from the system log before changing anything else.
• Reproduce with a single test user so you are not debugging a crowd.
• If it worked before, diff the config against the last known good, then open a vendor ticket with the timestamp and request id. Never send secrets or private keys.

Prevention

• Track credential and certificate expiry with alerts, not memory.
• Run a synthetic check per app daily so breakage pages you, not a user.
• Document mappings, URLs, and runbook steps where the next admin will find them.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstdg56RzQRnKJCFAnJCiwGQ

Resolved from the public thread: https://vectle.com/posts/pstdg56RzQRnKJCFAnJCiwGQ

Thread query: notion oauth restrictedtoworkspace install error

TL;DR: The Notion integration is restricted to a specific workspace - either it is an internal integration, which by design installs only in its home workspace, or the target workspace blocks outside integrations. Install it in the allowed workspace, or convert it to a public integration and complete Notion's review for cross-workspace distribution. The workspace admin decides which path applies.

Not specified by the original author.

TL;DR

Look the object up by listing the current workspace rather than trusting the stored id or name, remap the reference to the current id, and fail loudly when a listing has no match. Start in the Metabase admin panel, the question page, and the serialization export log, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Metabase saved question failed: ERROR relation does not exist for table in dashboard card query

Use this when

• You see this exact message or symptom in Metabase: Metabase saved question failed: ERROR relation does not exist for table in dashboard card query
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• Metabase fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the Metabase admin panel, the question page, and the serialization export log and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the saved question SQL or query builder definition, the dashboard parameter mapping, the database connection, and the collection the entity belongs to, and check the current listing of the named objects, the old versus new id or name, and the remapped reference in the config. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: look the object up by listing the current workspace rather than trusting the stored id or name, remap the reference to the current id, and fail loudly when a listing has no match. Verify: the corrected value or setting is visible in Metabase itself, not only in a local config file
4. Re-run the original operation on the single affected item first: open the card from the dashboard, run its question alone, fix the query or mapping, then reload the dashboard. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the card returning rows on the dashboard and the parameter filtering the connected cards as expected. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

Metabase saved question failed: ERROR relation does not exist for table in dashboard card query

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

Metabase version of this failure

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does metabase saved question failed: ERROR relation does not exist for table in dashboard card query keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Metabase 49 or later (open source or Pro), dashboard subscriptions and serialization, native SQL questions. The steps assume you can read the job or build log and change the named object in Metabase.

Why it happens

In Metabase, this failure usually means the reference the job uses points at an object that was renamed, merged, moved, or never created in this workspace, so the lookup returns nothing. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_qvOr00UyfszU9IaNzbjn0g

Resolved from the public thread: https://vectle.com/posts/pst_qvOr00UyfszU9IaNzbjn0g

Thread query: Metabase saved question failed: ERROR relation does not exist for table in dashboard card query

TL;DR: Look the object up by listing the current workspace rather than trusting the stored id or name, remap the reference to the current id, and fail loudly when a listing has no match. Start in the Metabase admin panel, the question page, and the serialization export log, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.