Error: Failed to get existing workspaces

Not specified by the original author.

Fix terraform "Error: Failed to get existing workspaces" (S3 backend)

TL;DR: terraform init cannot list workspaces in your S3 backend. Almost always the bucket does not exist yet, the region in the backend block is wrong, or your IAM identity lacks s3:ListBucket. Backend resources must exist before init, so create the bucket first, then re-run terraform init -reconfigure.

The error

Error: Failed to get existing workspaces: error listing S3 Bucket Objects:
NoSuchBucket: The specified bucket does not exist

Steps

1. Check the bucket exists: aws s3 ls s3://YOUR_STATE_BUCKET. Expected: the bucket is listed. If not, it was never created or the name is wrong.
2. Check the region in your backend "s3" block matches the bucket's real region. Expected: they match; a mismatch gives BucketRegionError instead.
3. Create the bucket: aws s3api create-bucket --bucket YOUR_STATE_BUCKET --region YOUR_REGION. Expected: the bucket is created.
4. Re-run terraform init -reconfigure. Expected: Terraform has been successfully initialized!

When this applies

• terraform init fails at "Initializing the backend" with "Failed to get existing workspaces" and an S3 error underneath.
• You just wired up the S3 backend and never created the bucket.

When it does NOT apply

• State lock errors at apply time. That is a locking problem on an existing backend, not a missing bucket.
• "Backend configuration changed". That is init noticing you edited the backend block; it wants -reconfigure or -migrate-state.

Tool and version compatibility

• Terraform CLI 0.12+ through 1.x. No provider needed; the S3 backend is built into the CLI. AWS CLI for the bucket checks.

Why it happens

Backend initialization is the first thing init does, and it lists existing workspaces to understand the state layout. Listing requires a bucket that exists, in the region you named, readable by your credentials. Any of those missing fails the listing before providers or modules are even considered.

Edge cases and pitfalls

• IAM needs s3:ListBucket, s3:GetObject, and s3:PutObject on the bucket and bucket/*. AccessDenied on init is the permissions variant of this same failure.
• Bucket names are globally unique. A name that "should" exist might belong to another account.
• This error also appears when the backend block uses variables or interpolation. Backend blocks only take literals; pass values with -backend-config=backend.hcl instead.

A troubleshooting guide records this exact failure: Error: Failed to get existing workspaces: error listing S3 Bucket Objects: NoSuchBucket on init. The verified fix was creating the backend bucket first, then running terraform init -reconfigure. Source: mchittineni/eks-terraform docs/troubleshooting.md, https://github.com/mchittineni/eks-terraform/blob/HEAD/docs/troubleshooting.md

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.

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.