needs a workspace or team ID

Not specified by the original author.

TL;DR

Use a personal access token with the official client rather than basic auth with an API key, which is the legacy pattern. Then add tasks one by one against the new project ID.

Steps

1. When you create Asana projects via the API, fetch the workspace or team ID first and include it in the create call; the project wont create without one. Then add tasks one by one against the new project ID. Use a personal access token with the official client rather than basic auth with an API key, which is the legacy pattern.

When to use

You are seeing this: When you create Asana projects via the API, fetch the workspace or team ID first and include it in the create call; the project wont create without one. Use this skill when you run into "Asana API: creating a project needs a workspace or team ID".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Stack Overflow #30601424 (accepted answer, 4 votes): the asker wanted to create projects with tasks from Python. The accepted answer: a project create call must include a workspace or team ID, which you look up from the API first, and then tasks are created separately against the new project.

Verified resolution: When you create Asana projects via the API, fetch the workspace or team ID first and include it in the create call; the project wont create without one. Then add tasks one by one against the new project ID. Use a personal access token with the official client rather than basic auth with an API key, which is the legacy pattern.

Source URL: https://stackoverflow.com/questions/30601424/how-can-i-create-a-new-project-with-tasks-in-asana-using-python

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.

TL;DR

Fix this in Help center by acting on the exact symptom first: scope the widget search to the brand identifier set in the widget configuration for this site, remove the shared default brand value, and search the widget on each brand site to confirm results stay in brand. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Help center embedded widget search returns results from the wrong brand

Use this when

• Work in Help center shows this exact symptom: Help center embedded widget search returns results from the wrong brand.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Help center, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: scope the widget search to the brand identifier set in the widget configuration for this site, remove the shared default brand value, and search the widget on each brand site to confirm results stay in brand. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Help center that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Help center embedded widget search returns results from the wrong brand

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - help center embedded widget search returns results from the wrong brand

The how to phrasing for the same problem in Help center. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Help center troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

The widget was installed with a shared configuration that carried the first brand identifier, so every site searched that brand catalogue regardless of which site the reader was on.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Help center at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

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

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

Thread query: help center embedded widget search returns results from the wrong brand

TL;DR: Fix this in Help center by acting on the exact symptom first: scope the widget search to the brand identifier set in the widget configuration for this site, remove the shared default brand value, and search the widget on each brand site to confirm results stay in brand. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.